yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sonymsam:
:victory:

:highfive: Nice!!! I will wait for it!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wickidmasshole:
You have no choice but to wait!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
Task is posting ROM pr0n...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
**** just got real up in here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vomer:
I call upon the mods to ban such profanity from this thread.... kids come here you know :D :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
****'s been real in this thread for a long time:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
Task you silly tease... The real question is what is working and what still needs to be fixed lol :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
The only things working are the page that shows the specs of the phone, the wifi (but only two bars), the cell service, the battery status, and the time and date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Oohhh insider info :p

You forgot to add the clock mod for center is working along with.................

:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
Hey task I flashed your new kernel and im getting some screen flicker. I wiped my cache and dalvik before flashing. I'm working on reproducing the issue and getting you a logcat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No need for a log cat. I'm not seeing any screen flicker. Also. There's nothing that was changed in respect to cause anything screen related. You can look at then source if you need. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Until this is ready for public use it doesn't really matter. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
Got it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There must be something behind the scenes on your device that would be causing this. Try and figure out if you've changed something recently and change it back if you can to see if that helps. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
The only thing i flashed recently was your new kernel. Haven't touched anything since your last release. I'm going to do full wipe and install your latest kernel again to see if I still get the flicker. No biggie though. I would rather put up with a flicker than touchwiz ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's a good idea. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I need new underwear.

SGS3 JB 4.1.2 Ktuned Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Task your new kernel is that 4.2 compatible? It's working well for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It will be once everything is finished. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Just wanted to post that both your latest test kernel and ktoonsez's latest test kernel have both stopped the black screen issue on my phone.

Not sure if both kernels went about doing it the same way or not, but whatever you did, it worked for me. Thanks, T&K!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
Also, installed the new kernel yesterday and so far today still no hiccups. phone wakes up beautifully as i command it to every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Task....Just wanted to take a chance and ask...did the devs give up on the whole Mic (using only the top/low recording volume) thing? Or is it still on the table?

Thanks for any insight. :thumbup:

PS. Devs meaning you and anybody else that contributes to the build or source. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm not sure. I haven't bothered myself with any of it because it doesn't effect me or how I user my phone. Too busy lately also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Understood and thanks for the reply!

I just really want your ROM but that does affect my use...one day....one day. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Remember sometimes a weird app running can affect basic function. Esp root apps.

Smells like updawg all in this piece...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
I did alot of searching before posting this issue, it has to do with the GPS. While there seems to be many posts that mention GPS issues none seem to be what I am experiencing. I have noticed this for the past 5 or 6 releases but I do not use my GPS very often so I never really cared to post it until now because I will be using it more often:

Steps:

- Turn on GPS open Maps or Navigation and I do not get the dot in the notification bar no matter what I do

-I can fix this by running an app called GpsFix, and select start fixing.

-After about 2 mins or so I will get the white dot showing in the notification bar and everything works fine in Maps or any GPS software.

-Reboot phone and I must redo these steps for it to work again

For some reason this fix will work perfectly for days, weeks, or basically until I reboot the phone and then I need to redo the procedure.

I have always ran stock kernel, clean installs, and never flashed a TW Sprint Rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
screen flicker when and where? in certain apps? need more info. i know in instagram theres an issue during the photo filter process, but if you disable hw overlays it fixes it.

but as far as that go, no flicker issues for me. try repairing permissions too maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
I actually remembered the hw overlay issue and so far no flickering. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Edit: have you try going back to stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Here's what I've noticed.... I've NEVER flashed a Sprint based ROM ever...

For the longest time I couldn't figure out WHY my GPS seemed to work perfectly on the 1st boot after a fresh flash of AOKP (or any non-TW ROM) but after I rebooted... the GPS logo wouldn't light up in my statusbar after turning GPS on and firing up Maps. Through trial and error... I discovered (for me, at least) that I need to turn GPS on about 10-30 seconds or so prior to firing up the Maps application. Then the GPS icon shows up right away and works and locks perfectly every time. I don't know why. I don't understand it. ANY of the GPS apps, did NOTHING to change this for me. On stock - the icon shows up immediately after turning it on and firing up Maps. But, this is AOKP and stock is stock. 2 different ROMs.. so the comparison is irrelevant. However, my expectations were based on my experience with the stock ROM so I was unduly applying those expectations to this ROM and expecting the SAME results which is just not right. Another observation, is that (again, just for me) - this experience with the GPS icon is the SAME no matter whether I'm running AOKP, CM10, Liquidismooth, PA or any other non-TW ROM. Again, I am not speaking for ANYONE else.... this has just been my experience.

Edit: OH and flashing back to stock did NOTHING to change this phenomenon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deggy:
I remember reading somewhere that CM10 and AOKP ROMs don't play well with our phone's GPS functionality. I'm on a stock based ROM from time to time and GPS work better on them .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
weird. my gps works fine still. jrock, have you tried going into settings, location access, at the bottom, click GPS source and select internal GPS antenna as location provider. i went in there just a lil while ago and noticed nothing was selected. so i selected internal gps. other than that, gps has been working great here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
I've tried that too and it doesn't change the phenomenon for me. Weird.

Edit: well, it's not weird... not all phones are created equal.

sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dagnus:
I've just gotten used not turning off my GPS.. it only polls for location in maps and any app that asks for your location. I too have the problem that if I restart, it takes a good 30 seconds for the gps notified to come on, but yeah... just leave GPS on and you're fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
My sister's husband said the same thing... Granted, he's running his SGS3 on stock Jellybean. I always figured leaving GPS on all the time would just help in running down the battery faster but he claims it doesn't hurt his battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
ha! well i basically redid exactly as you said and i too get the same thing. i turned off gps, rebooted, then turned it on and loaded maps right away. no gps icon. so i turned off gps again, rebooted the phone.. and this time, i turned on gps and waited about a minute before i loaded maps. and bam, theres that pesky lil icon in my status bar.

hmmmm interesting :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mest22:
My gps works fine used it plenty of times already ....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Interesting... Hey, I'm not complaining. I'm just glad the GPS works. I don't mind if I have to turn it on a few seconds before I load maps. That's an EASY trade off to avoid having to run Touchjiz. I HATE Touchjiz with a passion!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
ha im not complaining either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
I have the same thing. If I turn GPS off, sometimes it can take a couple of minutes... sometimes even 5 minutes to actually start up. I've just started leaving it on. Haven't noticed any real battery impact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not sure where you read this but I've never had any issues with GPS. I have to use GPS every day for work and it works 100% for me every time. Not really sure what to to others that are having issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Do you leave it on 24x7? Seems like all the reports and issues are with people turning it on and off...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nope. I only turn it on when I need to use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Mine turns on and locks every time and I use it randomly just to play around or to search for restaurants near by that are still open late at night lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
First time I experienced a flicker issue! I use MX Player for my movie and video viewing. When I exit out to the home screen after loading a video, the screen flickers every time. If I just load the app then close out, no flickering. Any video also, ones taken from my camera or imported ones. I tried playing these videos in DoubleTwist and also the built in one from the Gallery and when I exit, no flickering.

Phone wakes have been 100% spot on still though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
I didn't even expect you to say anything honestly. It's not a big deal as I'm fine with the way mine works. I was just pointing out my experience since dude mentioned issues with his GPS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This basically says its the app then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
its not a matter of leaving it on 24/7 since once i do the steps i posted after a reboot it works 100% of the time until the next reboot. in any case its not a big deal to run after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
yep. although i have used it on other roms and got no flicker. im just reporting in any flickering issues i get at all, SIR!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Posts deleted...

This is a development thread. Keep your opinions to yourself, or post them in the general section.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlove27:
Task, running the new kernel, I'm getting black screens during calls. The keys on the bottom light up, but not the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doritos93:
Seems like after a loss of signal, 12/2 doesn't recover it. Phone needs to be reboot in order to pick up signal again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhostetter:
Glad to see the thread opened.

Running 12/2 with new kernel and no issues. Full wipe before flash. Another great ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not sure what you're having an issue with here. Do you know how to read? Follow the simple rules that I provide in the OP, leave your personal opinions out of this thread, and contribute something here rather than take away from it dude. These are the kinds of posts that are ruining XDA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
*blabbers some sort of personal opinion*

on a more serious note... task is there anywhere one can reach u like gtalk or something.... im pretty sure i pmd u and it might have got lost a while back... im trying to start learning le aosp ways and i seem to be getting pooped on... but i cant go back to TW now... its to late. tw looks fugly and im not a themer. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I get too many pms a day that I stopped checking them pretty much. I barely have around 5 minutes to myself a day lately with my job, family, and trying to get this stuff on XDA done. I'll try and get a hold of you later to see what's up. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
It's nice being back on this ROM after testing TW JB... I'll never go back to TW again, it's pretty much cemented now. Only thing I miss is Smart Stay but I can certainly live without that. The 12/2 build is even better than the old 11/4 build I was running (obviously). I've gotten about 3 black wakeups in the past 5 hours or so, it hasn't been a problem for me, I might flash the other kernel though just to have the latest and greatest. Kudos to the creators task and ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. you should expect the black screens with the kernel packaged with the rom. you need to update to the latest kernel that is posted in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Puff3r:
Thank you for making the best ROM I have ever run. Saw this when I had my GS2 but never tried it. Regretting that decision now. Saw everyone drooling over the official 4.1 release by AT&T and can only assume they don't want the buttery smoothness we in this thread have found. You rock Task, thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Yeah, I figured that it would happen to some extent after reading this thread all day at work (or all week, but whos keeping track), but so far for me it hasn't been a real nuisance. Still worth correcting though, so might as well give 'er a flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vic_singh:
Can I use DSP Manager with this Rom? Cause I installed and it force close all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
12/2 is damn good. I get random UI crashes and MMS crashes (causes notification sound to stop working) but it's only once a day and I say it's a good chance to do my daily reboot. So no complaints another great thing I noticed is the MMS fix where the picture doesn't overlap the text anymore... Great job task! You sneaky ninja. Appreciate all you do shinobro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Yes, really kick ass work, Task!!

I hadn't flashed your new kernel until now... big diff. Even better than before.

Smells like updawg all in this piece...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chauleyboii:
Sup peeps bout to try this rom for the first time.....I see the latest is 12/3 but the download sayd 12/2.....just tryna make sure im downloading the latest!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The latest is 12.2.2012. Make to to flash the latest Underwear kernel fr 12.5.2012 in the OP too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
dat thong kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chauleyboii:
Koo thanks bout to download now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rockliveson123:
Do I have to anything after flashing the underwear kernel and wiping caches? Is it supposed to wake up the phone better? It seems I have to click the lock or home button 3 or 4 times to wake It. Thanks for your time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
Been on the new kernel for over 24 hours now and have not had a black screen yet. Would have happened at least twice by now on older kernel. So far so good, thanks task
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s2556:
Just wanted to say thanks for the awesome rom task. I've been rocking it for a while and had no issues at all, everything is butter!

Thanks for all the hard work man! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nystromproductions:
Hey task long time user and donater. Love the ROM as always but lately experienced some issues just looking for feedback.

- using navigation this week I experienced several reboots in mid navigation.

- still get black screen issues when trying to unlock ext.

- battery life seems to be shotty on some days more than others

Love the quick reply and all the other tweaks, did a full wipe before running 11.18.12. That's what I am running now. Just looking for some helpful feedback, thanks again for the great rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Update to the latest rom for support. Your running an outdated one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
You should probably upgrade to the newest build. 12/2 for the ROM and 12/5 for the kernel. Previous builds aren't supported. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
doh. had a couple black screens earlier. also had a random reboot. loaded the camera app, locked the screen, then hit the home button and the beautiful pink unicorn loading animation came up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Only current version is supported - that's clearly stated in the OP. And there's a kernel in the OP to flash after the 12/2 version that helps with the black screens a LOT. Battery life issues are more than likely due to signal issues with the area you're in causing the radio to poll more.

Get current, see what happens, and report back - more help is surely available then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
not sure why people ask about issues when running on an out dated version :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You should expect all of the above to happen. You're not running a supported version. Please update to the latest release to receive feedback and support in this thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
I'd say most of the time it's because they haven't read through the thread and good odds they don't even know where the OP is to check it. But hey just guessing here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
But why should I go to the first page? That's really old, and it can't possibly be relevant to my current problem, could it?

<sigh>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
I found that REGARDLESS what method I use after rebooting, GPS will still take around 2 minutes to start locating after an application that utilzes GPS starts. Therefore, as soon as I reboot my phone, all I do now is enable gps, open up GPS Test for literally a second or two (Maps works also, but I prefer GPS Test) and even though it won't show your location/notification bar notification, go ahead and close the application and then you can turn off GPS. The next time you need to use GPS (assuming it's past the typical 2-ish minutes it takes for GPS to start working), it'll work. It's as though GPS needs a GPS-dependent app to jumpstart it after rebooting for some reason even if the app only stays open for a second or two. My reason for replying in addition to everyone else is because my method only takes 15 secs vs. your method (which was my old method) that takes 2 or more minutes, so I wanted to save you time and show you that this workaround makes the GPS issue a pretty minimal issue.

P.S. I only enable GPS when I need it (after doing my initial "jumpstart" method of course). If you have any questions, feel free to PM me cause I feel like the GPS topic took up too much room recently in this thread already.

Check out Screebl. If you tweak the settings to your usage, it can work better than Smart Stay because it can even work in the dark since it doesn't use your camera.

Wow, while typing up this message, everyone else said what I was going to say, haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
I bet Task could put his SSN#, bank info and mother's maiden name in the OP and his funds would be totally and completely safe.

Old XDA saying, "If you ever want to hide anything, put it in your OP".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Well I'm back again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
8AF33405PV843061G. Thanks for the hard work Task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
Maybe cuz not everyone updates to the latest version all the time!? :confused: Sucks theres no support for those users here :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Because he can't reproduce the issue on his phone with the latest or unreleased release on it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Why wouldn't you? Bugs get fixed and updates typically improve a ROM. It makes no sense NOT to.

Edit: aside from the fact that the whole reason for an update is to iron out issues that plagued previous versions. It would cause Task a sh*tload of grief to support outdated versions and cause development progress to slow to a halt.

sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
yah i know, I tend to rock the newest version but sometimes, the older version runs better on my current setup. Im assuming that may be a reason why some people dont have the need to update regularly, its cuz they found a stable version that fits their need. When they complain about a bug, people tell the user to update as if the updated version has all the fixes and bugs removed. NBD just thinking out loud. :angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Not always are the issues fixed... but it's still best to have the newest version... at least you'll know for yourself is it fixed, without having to ask... and usually tons of other people report issues, so reading every post helps...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
may be not man, sometimes updating to a new version gives us changes in the user control or some bugs that were reported get fixed. sometimes tho, new bugs appear on the latest version that werent there before... Im just saying cuz Ive found myself reverting back to a previous version before just because it didnt have certain issues on my set up. Eitherway, im all for runing the latest version 99% of the time and I see why its just easier to make it a rule to not support outdated version. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
A) not a chat room - sorry.

B) If you're not on the current version, you can't ask for, or expect, support. If you want to use a previous version, fine, but the thread is to support the development of the ROM. Past version problem reports don't do that.

C) Please don't respond - still not a chat room - thanks.