yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
A) Q&A thread is for questions

B) if it was from a long time ago, try the new ROM, try it, and if you still have problems, then maybe this ROM isn't for your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psm510:
Okay, thanks. I appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Flash has always worked. Even back in the first couple builds of ICS that Task did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
After flashing the latest update I've encountered my first problem since installing a Task650 ROM (addict since March 2013).

When I open the Browser it loads half way then crashes...If I try it again, it's fine.

I've tried:

Opening from the app drawer not the home-screen (shortcut?).

Wiping cache.

Wiping Dalvik.

Every flash I perform I:

Format Data, Factory Reset, System wipe (ROM), cache, Dalvik cache...I clean house!

Thoughts?

Thanks for a great ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
My thoughts are that you need to post bugs in this thread with the proper information. It doesn't help the troubleshooting process without it. Otherwise it only creates clutter with all the guessing that has to take place when trying to figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
And what is the "proper information" you're looking for?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You need to read the OP before posting here. It has all the necessary info for these types of things. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
If you don't know how to post bug reports in a development forum then you need to spend some time learning. First thing is to read the first post. Next understand what you are doing. Flashing a rom is not something to be done lightly as it can leave you with a brick you can't return as you voided any and all warranty

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nomoiphone:
I knew better than to post my question. :(

I've read enough of your guy's responses regarding this subject but honestly it's confusing on how to meet your expectations. I'm no stranger to flashing (My Captivate, Note and S3 never saw the stock ROMS) but I am a novice when it comes to reporting bugs. I love this ROM and how active it is, that's one of the main reasons I switched from my previous ROM...It was stale.

I apologize for any "Clutter" I may have caused. I've been following this thread for a month...I should have followed my gut and kept my mouth shut and just continued lurking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Or....

Instead of "keeping your mouth shut" you could just take a few minutes to read the information that is provided in the OP which contains the FAQ which contains the info on how to report these types of things. If you did that you could be a contribution to this project that would be a benefit to this ROM and everyone that uses it. That's the whole point of me having this thread. This thread is for me to gather information to aid me in making this ROM better by fixing things, adding things, ect... If everyone just "lurked" then there would be no point in me posting these ROMs here because I could in all reality just do this on my own. Hopefully you will see what we are asking for and you will decide to just take a few minutes to review the information so that you can post your issues with the proper information. ;)

I don't think that I am asking for too much. You need to understand that I can't just guess what the issue you are having is. I need the information to be able to see the error, troubleshoot the error, and then fix the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Now I can view my pictures from the camera only if I open it from swiping to the right on the lockscreen. If I select the icon from my homescreen I get the blank image. And If I kill the app it doesn't work on either. This is after 3 full wipes. Any other info I can provide to troubleshoot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I would just wait to see if future updates might help you out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Try opening camera & toggling from external save directory in camera settings back to internal. Close camera app & re-open then set back to external save. Before all this be sure to clear cache/data for gallery first. It corrected mine.;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] torontomark:
I just saw this same problem just come up on my Captivate build as well - wait is the answer on this one - also have the same issue here and I know that this was wiped totally clean before I flashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task today I was taking pictures and I tried swiping to the left to view my pictures within the Camera app and it is showing blank for me as well not a big deal I am just reporting the issue which I see I am not the only one I will just wait for a future release ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This post doesn't belong here.

Reasons why:

1.) You stated yourself that it has already been reported. So why the need to clutter the thread with another? It doesn't help.

2.) You've provided no information to be able to troubleshoot the issue you are having. This is a development thread. Not a talk about bugs thread. We are here to fix things. Not just talk about them.

Please don't post these types of things in this thread as all it does is create unnecessary clutter. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
OK no problem sorry about that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
simply clearing the gallery cache will fix this issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIowaKid:
No it does not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes it does. If it doesnt work for you then thats fine. But unless you are going to provide some time of information and/or solution or workaround, I'm not quite sure what the point of this post is? Just wait to see of a future release will work better for you. I've stated this a few times already now. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please don't post the bs here. This is a development thread. This does nothing to help the development of this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Liptus:
Task you must really love developing because I would of got pissed off over 500 pages ago and just closed the thread lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Just cause it doesn't work for you doesn't mean it doesnt work.

Really? If you dont have anything constructive to post then dont post at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
TheIwoakid

Please keep your emotions to yourself. They do not belong here. I've already told you dude. This is a development thread. Treat it as one and I don't think you would be acting out like this. Please stop posting here. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Look I post when I have to. I try to keep this clean but everytime I turn around I have a bunch of non development based posts or posts that don't follow the proper reporting procedure. That I have to remove. You think I enjoy coming in here and cleaning up after people? Not in the least. Task has no issue with people posting as long as they follow simple rules in doing so. Bug reports without logcats are useless, but yet people keep posting. People seem to have forgotten this is a development forum and not a rom or support site.

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the Moderator

To all in this thread..... Please be advised when a Senior Moderator makes a request..... FOLLOW IT......... do not take it lightly, all that will get you is Club-Banned

Remember.......Post development related issues only, post respectfully, post on topic or do not post........

........It is that easy...... do not troll in here......do not post commentary....... post on topic.........

.........We thank you for your adherence to the Rules of XDA.........

The Moderators
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bob Simons:
whether to logcat when I can't capture an error...

Just a general question about logcats but not in relation to any specific issue. Is there a value in sending in logcats which don't capture a problem, like maybe when the phone locks up? Is it helpful possibly because it at least captures some configuration or settings info? I saw a response from Task a few days ago where someone said he didn't send logcats because he could not capture the condition but Task replied that in that particular case the logcat would have shown that a particular setting was engaged.

So I guess I'm asking how can I help if I can't capture the phone misbehaving. Just wanting to keep from lowering the signal to noise ratio.

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's a Q & A thread for these types of questions. And there is also information about the type of information needed in the FAQ depending on the circumstances.

Log cat for errors and force close type situations.

Last_kmesg for reboots
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
You're probs gonna burn my butt for this. But I was hoping you could include something to change the order of the buttons in quick reply because I am constantly pressing call thinking its reply. If you're gonna yell at me, just don't say anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? This is the internet dude. If you can take text via the internet as yelling then I think you might need to reconsider reading posts here on XDA. The quick reply buttons are fine how they are. You can remove the call feature if you choose so you won't push it on accident. Please flow the rules and read the OP before posting here. There is a Q & A link obviously posted in the OP for these types of things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
It wasn't a question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You said you were hoping that I could include something dude. Please don't play this game here. Its not the place. You implied a question. This is a development thread. Please treat it as one. Thanks.

I'm not sure why this is so hard for some of you. There is a Q & A thread for questions. Just use it. Leave this thread for bug reports so I can fix issues when they come up. I'm not asking for too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GNEXUZ:
Been using this ROM for several months. Just wanted to say, love the work brotha. Great battery life, incredibly smooth, no lag, no complaints. :thumbup:

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Now that the Q & A thread has been found, I can open this thread back up. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theREDlegion:
task650, your 4/19 build with ktoonsez 4/19 - 3.4.41 kernel has got to be the smoothest android experience so far. Have been flashing numerous ROM and Kernel combinations over the past eight months and can't imagine that it could get any smoother that this combo. But i won't stop flashing, and to you dev's much respect and thanks for getting our devices this far.

Running for about 15 hours straight. No FC's no bugs are showing up yet.

DEVICE - Rogers SGH-i747M

BASEBAND - I747MVLLE8 stock ROGERS modem

KERNEL - 3.4.41-KT747 Ktoonsez

ROM - Task650 4.2.2 JDQ39 build 4.19.2013
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
Hey anybody else have the issue where any word with 'gg' in it shows as 'fi' ex. plugged=plufied shrugged =shrufied

It has gotten to be pretty annoying
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
http://xdaforums.com/showpost.php?p=38843439&postcount=24316

This is a development thread. There is a Q & A thread obviously linked in the OP for these types of things. Please use it. Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Covart:
Is it bufiing you?

It isn't the ROM. I have no such issue. Use another keyboard app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
This only happens with YOUR rom. That's why I'm here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Did YOU decide not to read my post? There is a Q & A Thread for my ROM. If you are not posting legitimate bugs (logcats, last_kmeg, ect...) here and want to know if someone else is experiencing something, then you need to take it to the Q & A thread that is linked in the OP. You also need to read the OP before posting here as you would've seen the link. As I stated before. This is a development thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rflnc1:
No..this only happens with YOUR device..here's the Q&A for this ROM.notice how it's not in the development section..http://xdaforums.com/showthread.php?t=1781242
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 78Staff:
Task, had a random reboot today, first one ever so haven't seen any issues with phone or builds previously. 4/19, Last_kmsg attached, lots of "alarms/devices failed to suspend messages / error -16" but at the very end it states no errors found, so not sure it will be helpful.

To be honest, could just be a completely random deal on my end...since I had just shut the screen off with the power button maybe I did something/fat fingered when I sat the phone down, as it occurred right after that. :rolleyes: Anyway figured I'd let you look to see if you saw anything out of the ordinary.

'78
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Whenever I get the time to release another update it will be a cool one.

AOKPs Ribbons feature is pretty cool. It includes Lockscreen shortcuts, Quick settings shortcuts, Notification shortcuts, AOKP Slide shortcuts (Which is like what PIE does).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stankydanky702:
I'm at the point of only looking at this thread for when updates are posted.. Cuz the only posts I see now days are peeps telling other peeps to go to the q&a threads .......

Thanks for messing it up for everyone else guys lol

Sent from my DANKMOBILE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then they are helping. If something doesn't belong here then that is exactly what they are supposed to do. Not sure I see the problem here dude? Either way. Can you please keep these types of posts to yourself. It has no benefit here and will only start arguments back and forth. As im sure you can understand. Thanks.

P.S- Unless you're going to post a bug with the appropriate information you shouldn't need this thread anyways. This threads purpose is for development. Anything else belongs in the Q & A thread or elsewhere. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Seems more like Unity than Pie.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Next update looks awesome. Now I'm going to be checking XDA every 5 minutes:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamkhanh:
F5 F5 F5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Browsing in Chrome when I got a random reboot. Last_kmsg attached. Hope it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Chrome = A horrible browser for android.

I would expect issues from it. You're not the only one that has issues with it. Thousands of people running all different ROMs have reported the same thing.

I don't support 3rd part apps so there's not much I can do for you about this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jriv:
So I've noticed that I don't get random reboots when my phone is charging but I get about 4 a day when not plugged in and its either when I'm using internet or the other time is when I try to open the camera up. But like I said if my phone is plugged in it doesn't matter what in doing it never reboots

sent from a guy living in a van down by the river
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flammingcamel:
Up your voltage from CPU range 486-1242 by 25 MV. Then try those tasks. Sounds like its just causing your phone to lag hard without the proper power. Also Dont use noop io scheduler. Zen is working very well for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
What Browser do you use/suggest?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dav5049915:
Obviously the stock one that is packaged with the room...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
But the stock one doesn't sync with Google anymore...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I think he was being sarcastic..

Now guys, this sort of question belongs in the Q&A section (not the ROM's one). There are already plenty of threads about browsers on this forum, just use the search ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You need to post these types of things with the appropriate information. Otherwise they don't help the troubleshooting process nor do they belong here. We're here to fix bugs. Not just talk about them. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkstar765:
The NFC fast toggle isn't working for me. Sorry if this has been addressed. NFC does work fine tho.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Works fine here, log cat or post in Q&A thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkstar765:
Will do
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dwk11:
If you restarted your phone, all you need to do is go back to ROM control, go to toggles, and reapply the toggles style. I don't know if that just reapplies "superuser" priviliges to allow all toggles to work. Task can correct me if I'm wrong but there's your fix. Do that everytime you decide to reboot.

I never commented on it because it's an easy fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcipher:
First time i've ever had my phone reboot spontaneously. Last_kmsg attached.

This is a completely clean flash - did not even restore any data - wiped everything as per OP, installed ROM, setup as a new phone.

Been running flawlessly until this reboot.

Let me know if you need / want any more info.

Thanks for all of your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] admrusty:
I also had a random reboot from an otherwise fine install. One yesterday as well while charging. Fully wiped as usual. Based on my OS uptime it seems to have rebooted when I left my house this afternoon and off my wifi. Thanks for the great ROM!

http://db.tt/Quy4Jeox
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radiumX:
Is current build stlil using linaro tool chain?

Hey task, I had a couple questions. A while back when you updated the kernel to, well I think it was the update to 3.8, some phones began having trouble, I was wondering if this was still the case. My phone was one of the phones that didn't like the 3.8 kernel.

I was also wondering if you are still using the linaro toolchain for the current build, or if it was just for the one labled linaro take 2?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RPelham:
You can see from the change log in the OP if linaro is still being used. I'm pretty sure Task isn't going to put "kept feature" for each release. If it was removed he would have put it in the logs.

As for the kernel, it is version 3.4. Not everyone had problems with it, only way to find out if you are having issues is to flash it. No one else will be able to tell you if it will work for you.

p.s. its working great for me!

p.s.s. further questions need to be asked in Q&A. This is a development thread used to report bugs, (using the correct method of course) and to further the development of this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerseymarine:
Glad to be back using this ROM. This past update fixed my phones issue with locking up on phone calls. Awesome job. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutbdat:
I Did a clean install and am having flickering issues as well (running 4/19 stock everything)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I would try again then. Not seeing it myself and haven't for quite some time now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
Deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
Damn this release is so stable its going to be hard to re-flash, THANK YOU SO MUCH TSK not a single problem to report. SMOOOTH....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Yea, I almost have nothing to complain about... again. This Rom is just getting boring. I may have to switch to a crappy one.

-- nice story, bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
This ROM has been nothing but no money loved your ROM task on my galaxy s2 and was excited to use your ROM when. I got my s3 last week! Thank u again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
This hurt my brain to try and read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Lol yes I never use proper punctuation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thoughtMaze:
crushed them

You crushed all my problems Task, good work.

all that's left is to hack the Gibson .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Hey Task!

Fixed my last issue (got a phone swap through ATT and that now works just fine with 3.4 kernel :) However, whenever I flash AOKP (I've tried 3.0 and 3.4) I get "can't connect to the camera". It worked on stock, and I haven't seen this issue before. I even unrooted back to stock, rerooted, and did a fresh flash following OP instructions. I've tried wiping everything again and reflashing. Didn't restore any apps, didn't install any apps. Any ideas based on this logcat? Seems to show the error in this part. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What do you mean it worked on stock? This is an AOSP based ROM thread so I'm not sure what the reference to stock is supposed to mean? Camera works fine. Redownload the rom and try again. You will just have to keep trying until it works for you. Please read the OP before posting in this thread.

From the OP

7.) If you're going to post here, keep it to this ROM and this ROM only (unless its fun as mentioned above). It is useless to compare to Stock ROMs, CM10 ROMS, ect..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
All I was saying is that the camera itself was fine, wasn't comparing ROMs. I have redownloaded ROM and GAPPS 3 times, and flashed. There's a bunch of errors in the logcat section I attached. Do you see anything in there for me to troubleshoot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I dont have time to look at the logcat right now and I'm not at a computer to look. But with you being the only person to report this out of thousands of users to download and install this ROM, it's something that's caught up on your end. That's why I'm telling you to redownload and try again. Make sure you are formatting system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Thanks man, I'm assuming so, just a matter of figuring out what haha. I'll try again here and see if I can get it going. I'll edit this post if I can get it or not :) I haven't seen the camera thing since like June or July haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Have you tried clearing data for gallery?

I was having this issue until I cleared the data for gallery and did a restart.