yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then i would use another ROM for now. With all the new stuff being implemented lately I dont think I'm going to mess around screwing with something that I don't see as broken. That can open up a whole new can of worms that I really dont have the time for. So you have a couple options:

1.) Revert to a prior release.

2.) Flash a different ROM.

3.) Wait for a future release (Which I dont think anything will change for you)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
This catlog LOL

http://dl.dropbox.com/u/43004135/2013-04-07-08-50-25.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
So you fully wiped your device and upped the min clock speed before posting this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ralphie1267:
For me the scrolling issue is getting better as time goes on. seems for me that my phone is settling in has not happened today at all. And been using phone all morning.. Everything else running awesome as usual. Thanks for sharing your rom.. Love it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dfg187:
sweet. great update so far. phone sleeping, clock fixed everything working great.

for the kernel same procedure. flash and wipe cache and dalvic?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I had this issue along with random freezes and reboots until I upped the Min clock speed to 486.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
I was getting the same scrolling problem (running underwear kernel 4-5 release) but just like above today it hasn't happened at all. Seems like a two day settling period then smooth sailings from there.

Underwear settings:

Interactive

Row

Min - 486

Max - 1512

Everything else stock settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ralphie1267:
:thumbup: thank you for new kernel update today. fixed my scrolling issue totally. Phone is once again perfect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdelponte:
what version of CWM?

I have been searching all over and can't find the answer.

Should i use CWM 5.5.0.4 to flash the latest AOKP 4/5/13? or should i use CWM 6.0.3.0?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
if you're flashing manually (instead of OTA) you can use whatever you want. If you have issues, you're likely to just hear "use TWRP" since it's considerably better now. But CWM should work fine for a manual flash. OTA is touchier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
I've also been having the scroll issue. I've never flashed anything else, went straight from stock. I'm using the same settings as below. I've also never dirty flashed. I wasn't going to report it because I figured it was a side effect of replacing broken glass myself. Since I've never flashed anything else would a logcat be helpful from me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
How long ago did you flash? This problem seems to be going away after a couple of days of use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
I flashed shortly after Task posted the update on Friday. The only reason I said anything is because I've never flashed anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then you are using an old outdated kernel. Not sure why you haven't looked at the OP of the ROM thread and I even posted it in this very thread not long ago. Please always at least look at the last couple pages of each thread you come into before posting. It can help cut down on unnecessary posts like this.

P.S- The kernel is even posted on the same page as your first post about this dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
Sorry I haven't updated. Flashing while running around all day in an ambulance isn't a good mix. The only reason I said anything and offered a logcat is because I've never run ktoon's kernel, so there is no chance my phone has been corrupted. I know better than to post bug reports on previous versions, but I didn't realize all discussion of previous versions was verboten once an update was posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhoenixBlitz:
I've been experiencing some weird problems, I can't seem to wake my phone , the phone itself is running, but pressing either the power button or the home button won't wake. I have to pull the battery and it seems that when I place it back in it will automatically reboot rather than having the manually boot it on like normal. This even happens when I am charging the device, it'll be plugged in with the LED on and when I unplug the LED turns off and if I plug it back in it will turn back on. Does anybody know what is happening?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reup247:
This new test kernel seems to be working flawlessly on my phone. Thanks Task! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Hmm , so what are the new governors and sios in this latest kernel build? I'm curious to know before flashing :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Kernels take about 4 seconds to flash. If you're going to flash it, just set aside 10 seconds of your time. If not. Then use those 10 seconds for something else. I would just recommend flashing it considering its updated and has some necessary fixes.

P.S- I have no clue what sios is so it's probably not. But source is always available for you guys to look at. Its the most accurate change log ever. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidJiuJitsu:
I tried the new 4/7 kernel a few times, even with a fresh clean wipe with the 4/5 ROM and it is poisonous to my phone. It goes into and extreme reboot loop where it even took me a few tries to get it to restart into recovery.

My question is, I wanted to try and get a last_kmsg, but my phone won't stay on long enough for me to grab it. The phone literally reboots immediately after i slide from the lock screen. Everything is stock from a fresh install. Is there any other way to grab one from recovery or another source?

I managed to get it back up and running smoothly with the 4/5 ROM/kernel combination, but would like to try and get the last_kmsg from the 4/7 kernel - in case there is any pertinent information within.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
With you being the only one this is happening to a last_kmsg isn't going to help as I have been running this kernel since last night with absolutely no issues. If its not working for you then don't use it. You said that the 4/5 version is working for you so I would stick to that. Maybe a future release will work for you. Who knows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuRock:
Last 2 updates I have been experiencing freeze ups usually when on a phone call. Just stays on the call screen till I have to pull battery. I always do full wipes and never touch anything in performance control, any suggestions? Thanks..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Two suggestions.

1.) You could post with the proper information so some troubleshooting can take place.

2.) You could revert to a previous release that was working for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
This has happened to me once on each of the last two builds, maybe first call of each? Task makes dozens of calls a day and would be aware of it by now if it was a bug issue. If it's on every call, I'd try to wait it out and grab a logcat.

Either way though, my whole point of posting was to mention that with my experience, it was not necessary to pull the battery to reset the phone. Holding the power button for 30-40 seconds rebooted it. I don't think I've ever had to pull the battery on the phone, just hold the power button longer/again.

Sent from my SGSIII on Task's AOKP

Try a new Task650 AOKP boot animation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Up your min clock speed to 486 like mentioned in a few posts here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't need to up anything. I can run at any speeds I choose just fine.

But either way. This is not working for everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuRock:
Thank u sir. I know log cats are the best form of looking for the issue but I hate cats:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's fine. You can hate cats and all. But I just figured you would like the issue to get fixed and most likely in the end help others that are having the same issue. That is exactly what this thread is for. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuRock:
Thanks for your input. It just happened once so far on the last update so I'll just wait and see if it continues, than I guess I will have to throw the cat on the log:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] freshiem:
I had this same issue, everything stock, made a call, got a freeze, upped to 486 still got freeze on calls, the way i got it to work perfectly was to completely re-install (wipe etc etc) and go to 486 min speed as soon as the phone restarted. Works perfectly now - 2 days and about 15 phone calls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Task,

On the newest kernel/rom version, my launcher/systemUI crashes every 15-20 seconds. It crashes back to the boot screen (the unicorn). I'm not sure what you need but I see a bunch of errors in a logcat. Is this helpful? If not, what do you need? Thanks Task!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Sounds like you didn't do a clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
These are user errors. Not ROM errors. You need to follow ALL of the installation instructions that are in the OP of the ROM thread (FULLY WIPE YOUR DEVICE) and you won't be having these issues. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
I did. I wiped system/factory reset/cache/dalvik cache. After the first time, I went back in and did everything again. I flashed in this order:

4-5 rom

gapps 3-4

kernel you posted yesterday

The only app I installed was titanium backup (I didn't run the restore yet), and updated novalauncher/search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Should probably factory reset.

Also, flash only once, duno why you flash 4-5??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
That's what I meant by format data :-X my bad. What do you mean flash once? 4-5 is the newest rom, and 4-7 is the kernel he posted later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This release might not be a release for you then. Not really sure what to tell you. But I don't see factory reset in your post. It's very clear that that needs to be done in the installation instructions. The latest release and updated kernel combo is working just fine without anything you have mentioned for 99% of the users. I would redownload, fully wipe, reflash. If that doesn't work then I would revert to a prior release and wait for the next one to see if it works better for you. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Woah, sorry. You confused me.

I guess that release is simply not good for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
4.2.2 :eek:

I miss my SGSiii
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Yeah that was my bad, I did the top 4 wipes in TWRP 2.4. I didn't format data, I did factory reset. I got my words mixed up :) Could this be my phone not liking the new kernel? The last release that worked for me is 3-13. I always factory reset, system, cache, and dalvik if I have any issues. I'll try another download and see if that is possibly the issue, but I do see a bunch of systemerrors in the logcat, but I have no idea how to read them :-X

EDIT: Just retried again. Didn't install anything at all, or change any options. Put in my google stuff after boot, selected nova as my launcher and let it sit. After a few minutes, moved 1 screen to the right, and 1 back and it froze again. If I hit the hard buttons on the bottom, the lights come on on them and I get the little vibrate. But the screen does nothing. I've been having some issues on 3-13 lately where my screen doesn't turn back on until I reboot (I can still reboot if I find the buttons)... I wonder if my phone is on it's way out...

EDIT2: Flashed 4-5 release and gapps. Rebooted until frozen. Did an ADB reboot and went into recovery. Flashed 4-7 kernel and wiped cache & dalvik again. About 5 mins now and haven't locked up yet... Knock on wood...

EDIT3: Spoke too soon... Back to 3-13. My phone must not like to 3.4 kernel for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Replied to the wrong post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pizzanova:
This is my first post. You have produced a terrific rom but in the interest of aiding in development I need to advise that 'humblehyper' is not the only one experiencing 'phantom scrolling'. I have little to add to troubleshooting except that I always wipe factory reset system cache dailvik and have been experiencing this issue since the 3/31 release, using both the 3/31 and the newest underwear. I have tried raising min cpu to 486, with no effect and also completed the entire wipe/installation process several times. Admittedly the 'phantom scrolling' is most apparent in a 3rd party app called 'moon+ reader' but I have also seen the condition on Google Chrome. The symptom does not occur on the 3/13 release. My apologies in advance if this represents a "me too" post. or if I have somehow missposted or left out critical info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The issue has been fixed. You are referring to an old post as this issue was resolved. You also have given no information for any troubleshooting to begin so you will need to fix the issue you are having yourself. Also. I do not support 3rd party apps. If you are having an issue with a 3rd party app then you will need to take those issues up with the developer of those apps. If the OP of this thread was read before posting then you would know that there definitely is some critical information left out of this post. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Issue with voice to text in MMS and in general.

Running the amazing AOKP 4.5 Linux 4.3 version with KT's kernel.

Followed instructions perfectly, only issue is when I click the microphone to say anything, it FC's and shows Google Search not responding. (I made sure to set language to English)

Tried to wipe, wipe, fix permissions, and no go.

Tried wipe, wipe Dal, reflash Gapps, wipe, wipe, fix permissions, still no go.

Any other suggestions, or am I s.o.l?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This isn't an issue with this ROM. Google Search is a 3rd party app and you need to update it in the Play Store. Please search next time before posting as this has been beaten to death already in this thread and the ROM thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
My bad. No search function within threads on my XDA app. I'll throw a tip in the moron jar on Friday for the inconvenience.

No hard feelings? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It's no inconvenience for me. But it could be for the next user. Who knows around here. Just reminding you to search before posting. Doing so will help keep the clutter down and keep the most relevant issues current. :D

P.S- I have a very helpful tip for your tip jar. Lol. You have a very nice device with a very nice browser that works just as computer would. You can search with it. ;) :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
:rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illegalchaos:
That search searches forums, not threads. One has to open the thread in browser to search for specific queries within thread.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Ahhh touche.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
I **** you not, my search for "Galaxy S3 Google Search force closing" didn't redirect me to this thread or anything else particularly helpful, tbh.

But regardless, thanks again, and thanks for this incredible ROM. I kinda feel bad for whoever hasn't tried it. :thumbup::thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
:banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Is there a mirror for the newest kernel? Mediafire is giving me errors left and right. Tia
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No there isn't. I just tested the link and it works just fine. Downloaded it in 11 seconds. I would try again or use your computer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Alrighty. I'll figure it out then.

Failed on my n7 too, both chrome. Tried stock browser and it worked fine. Never had that happen before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
screen scrambling

hey task

so i got a logcat of my situation

the background of the screen will start scrambling

the only thing that fixes it is resetting the phone.

its been installed properly to the op.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I've already told you what to do. Revert to a prior release that worked for you. Things are actively being worked on and I don't think it's feasible in the amount of time to look into something that only 1-2% of the users are experiencing at the moment. Please try keep up on source so that you can see what's going on. Things are changing. Things are happening. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
sounds good. thanks man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
I've done a few google searches to see if there was a recent issue with this, but couldn't find any clear answers. I haven't had this issue in months.... Lately my mms app when opened shows a Downloading.... Message. That's it. Only solved through a reboot. Last time it was caused by me syncing contacts through facebook, but I've uninstalled anything related to that and it still is having issues. Any idea?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Give it a day - AT&T is probably screwed up in your area again ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
D@*n you Att! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carpboy:
Error 7

Anyone have any ideas what causes this? Using CWM I haven't had this up to 3.6.13. Just tried 4.5 and 4.9 and I am getting it.

Easily cleared by removing the build assert, I'm just curious as to what it means, if anything.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What's causing what? You haven't even stated what the issue is other than "this".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carpboy:
That would be Q&A OP post 1 bullet #16.

Sorry, I figured "error 7" was unique to flashing from recovery and thus didn't require further explanation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I didn't see error 7 in your post. That's why I asked. Its in your title but not noticeable. Please always put the subject in the post itself. That way nothing is missed. Thanks.

You're not using the right recovery. You need to update. That's what's causing it. There is already a ton of info around here on the subject.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
so I just tried installing the new ROM And ran into the same issue as the last build with getting stuck in a bootloop. This is the same issue I have when installing an external kernel so I know it must be a kernel issue. anyway to get around this by chance? Otherwise I will just stick to the March 9th build. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Are you sure you have the right thread?

There is no March 9 build. Only March 6 or 10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PearsonDKA:
So uh, anyone experiencing a loud screeching sound when listening to music/watching videos? It occurs randomly but frequently. I experienced this before a few months ago when playing around with different kernels where as some of them had it and others didn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slawcop`:
Nope..using poweramp and Google play no problems...start over wipe reinstall
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] multiduplikator:
Hi again,

Just wanted to let you know that the clicks when rw/off audio are gone with 4.9.

However the stutter of main playback while overlay sound is still there, but better.

Is there a system setting for default audio buffer size or something alike?

Cheers and thanks again for the hard work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task on 4/5 I had the issue where the LED settings would not get Superuser permission for the ROM control settings to stick, now on 4/9 I am having the same issue by any chance did you make any changes to this on 4/9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Yes, I was off by a day, going by memory... Anyway, never had a problem with this ROM until the latest kernel was put in, and I've flashed dozens of his ROMs before. Just wondering if it's just my phone and for some reason it just won't "take" this kernel. I had the same reboot issue when trying to install several of ktoonez's kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
And it's been said at least once a page - if your phone doesn't like the kernel (and many don't yet) revert to a 3.0 version and wait for the 3.4 version to get more stable. This is a brand new kernel and still a WIP ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
By any chance are you able to turn on the charging LED lights? For some reason it does not work for me :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
We did this a couple of days ago - I still can't get the toggle to stick. But I don't think you've submitted a catlog or anything that would help task, and it will work when it does...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Not a problem I was just wondering if you was having the same problem, I will wait until the next release :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Thanks, I figured as much. However I missed the discussion somehow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PearsonDKA:
Lmao. Wow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Task doesn't sugar coat his answers. Now would be a good time for you to get used to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Figured I'd ask questions here instead of the development thread and get flamed lol. In performance control the CPU doesn't drop below 486 even if I have 384 chosen. I'm guessing that is correct? Just making sure I wasn't doing something wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not correct. It drops to whatever you set it at.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Got it. I had to move the min slider up then back down. Was wondering why it showed 384 and 192 as unused states but I done got er goin. Sorry for my duh-ness. Gonna play some halo now. ;)