yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I experienced fc's with this ROM the first time I flashed but realized I dirty flashed because I got interrupted and hurried it, forgot to factory reset and wipe data . Made sure I did a clean flash and no issues since.

---------- Post added at 07:41 PM ---------- Previous post was at 07:32 PM ----------

man, tough crowd here :eek:........I saw a few posts concerning poor battery life and thought I would respond that it's no issue with this release so far. Better battery life than I have experienced with other ROM's using the same settings/apps and use. No way to do an apples to apples comparison.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
Task, for your latest version 3/4 is the "Crashes in Apps fixed" listed within your change log for Gapps only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Re: [Q&A] AOKP SGH-I747 (task650)

cLock widget not getting weather data and custom location fails as well. anyone got a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Anyone having boot loop issues? First time I've ever experienced a problem with one of Task's ROMS. I have a feeling it's kernel related as I've had problems with a certain i/o scheduler in the past with my phone (don't remember exactly which one it was), but my phone locks up when I got inot performance control.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Quick search would cover this - either a Yahoo API change or weather stations down. Working fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerseymarine:
Re: [Q&A] AOKP SGH-I747 (task650)

I am trying to download the 3.13 version to see if my phone will finally stop locking up on calls but it say the file is not on the server. This a glitch or was it removed for good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I've already answered this a few times. All old build are on goo.im. All you need to do is look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please follow XDA Rules and search before posting. Not only is this issue all over XDA forums, but it has been talked about here all day. Also. You could always check source every once in a while to see what's happening. I make it open and available for everyone to see. https://github.com/task650/android_...mmit/53f600296ed3e467546710d44ea045a96d573613
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Re: [Q&A] AOKP SGH-I747 (task650)

I understand how long it takes to flash a rom. Most likely wouldn't be able to tell if there's any issues within 28 seconds though, let alone 28 minutes.

Secondly, I was simply asking if the people who were having the same issue as me before are still having the same issue now. It would give me a better idea whether I should try flashing the latest rom or not. Using your logic, since all devices are different, nobody should ever ask "is anyone else having this or that issue?". I thought this is the thread where people should be posting those types of questions. If I was having the same issue as person B with release 3/29, I would take that into consideration if that same person is having no issues with release 4/03. Yes I know those release dates may be wrong but I'm trying to make a point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Well it's a good thing that I never said anything about you being able to notice if anything is wrong in 28 seconds then. Not sure where you got that info from. ;) But either way. It looks as though you just can't grasp the concept of these devices not being created equal. Well. With that being something that is very well known, even if the people that were having issues aren't having those same issues anymore on the latest release doesn't mean that you will be as lucky. That's just how it works and is a fact. This site is not a "Make my phone COOL!" site dude. Even though this stuff here does exactly that. It's a development site. If everyone used your logic when flashing ROMs then nothing would ever progress. We as developers post this stuff for everyone to test and give information back in order to fix and make things better. So for you to sit around asking "Does this still happen" and "Is anyone else having this happen..." defeats the whole purpose as to why I even release these ROMs publicly. So the moral of my story here is asking why you won't be part of the process instead of part of the problem?

P.S- Before you go taking offense to this (it's not intended that way), all I'm saying is that it's obvious that you are using this ROM. So it means that you like it. Why not give back to the development and help with at least testing and reporting with info that can help make it better?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
Re: [Q&A] AOKP SGH-I747 (task650)

Your change log says "Crashes in Apps fixed"... What apps is this related to? Gapps? Any apps you download from Google Play? Specific system apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Re: [Q&A] AOKP SGH-I747 (task650)

There was a whole 3 days worth of complaints of apps crashing without a force close. ??? :what: :screwy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes it does say that. I think between this thread and the ROM threads posts these last couple days explains this pretty well. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Re: [Q&A] AOKP SGH-I747 (task650)

Yes I do use this rom and yes I like it. And I thank you for your hard work you put into it. I no longer run the latest releases anymore because I was having issues after you implemented the new 3.4 kernel. When I offered to give log cats or last_kmsg you said don't bother, to just revert to a prior release because you stopped caring about the phone freezing while on a call. So that's what I did. I restored a working nandroid and now use the 03/06 release as my dd. That also means that I can't really help test your newest releases if I'm not running them.

Trust me I've tried being a part of the process rather than the problem. I offered the small suggestion a while back about implementing the cm calculator because it's simple and offers many more features. So I figured why not offer the suggestion to help development of the rom, esp since I had already extracted it and installed it on your rom with no issues. I was told (not by you) to just do it myself. This was before you later added it to the rom for more functionality as stated in your op (3/21)

I do grasp the concept that not all devices are created equally. Just to clarify, I was not stating that if the 04/03 release worked fine with person B that it would work for me. I was just looking to take something like that into consideration when making the decision to flash the newest version and test things out. I've tried other roms. I don't like them for the most part. That's why I run yours. But if I'm told to revert to a prior release, I can't really help much. Anyways I'll drop it. When I have some free time I may try flashing the newest version you have just to see how it runs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Then on that note. Just take into consideration that not all devices are created equally and no matter what anyone says that it doesn't apply to your device. ;) Its as simple as that. It eliminates the the Q & A thread being clogged up with the "Is anyone else experiencing..." posts that never actually fix issues and/or doesn't help me to debug that issues at hand. Also. When you guys were flooding me with log cats and I told you guys to back off with them, the kernel was in its very, very beginning stages and those log cats were of no use. That's pretty standard considering commits were already in place before those log cats were even presented. That's just how it goes. Staying on prior releases with nothing to debug defeats the purpose of what I'm trying to accomplish here is what I'm saying. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] steelcity:
Something is bugging me about the camera, not sure if it is just my phone or if it is like this for everybody. When i take a picture that uses the flash (specifically in very dark areas) the screen display is still dark even when the flash is on, so I can't really see how the picture is going to look (or if i'm pointing it at the right place). I downloaded a third party camera app and when the flash lights up so does the display. Obviously I can just use the third party app but I like the stock one better for several reasons so I am wondering if there is anything I can do to fix this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
Re: [Q&A] AOKP SGH-I747 (task650)

Here is a sample video with AOKP.

As u can see if I go close to the lettering it is fuzzy

https://www.youtube.com/watch?v=xVQq6HybdkY&feature=youtube_gdata_player
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Are you planning on writing code to make an attempt to make the camera settings more to your liking or something? I'm not really sure I understand what the video is about?

P.S- I'm pretty sure that you were the one I was telling that this is an AOSP based ROM earlier today. You really need to search around here on XDA and Google to educate yourself a little with what that means. We do not have access to the closed source drivers that are in touchwhiz based ROMs dude. That's means we're stuck with back porting and modifying the open sourced drivers that we have available to work with this device so that are camera will even work. If you want something that is on a touchwhiz based ROM then you need to use a touchwhiz based ROM. That's just how it is. Otherwise you will just have to be content with what we have available to us. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
so ive been trying to find out how to be able to have shortcuts (not widgets) on lockscreen and have a security code.

---------- Post added at 05:22 AM ---------- Previous post was at 05:16 AM ----------

sorry i was not trying to upset you but i was putting that up to show you what i am experiencing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Re: [Q&A] AOKP SGH-I747 (task650)

This is something that has also been mentioned before. You cannot have lock screen shortcuts and a password from what I remember. It would be pretty sweet, but I'm happy we still have lock screen shortcuts. I remember a while back task was going to discontinue them (until the OS was near finished) because he kept having to modify them. Extra feature or extra security? Your choice, but you can't have both. Unless your job requires it or you are cheating on your girlfriend, you don't really need it. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm not upset at all. I'm just trying to get you to understand that this is an AOSP based ROM dude. We don't have access to all the closed source proprietaries (like the camera drivers for example) that touchwhiz based ROMs have. My whole point is that if some of these things are something that you cannot stand, then you will need to flash a touchwhiz ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Nice

New version still had same problem with Playstore........same fix for me......opened playstore 3 times each time closing on it's own......4th time all is well. Don't know why it works that way but it does work and all is well with my S3.

Thanks Task for your hard/persistent work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
cannot boot into recovery

deleted, flashed incorrect file - my bad. All is good in the hood. Thanks Tasks for awesome build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] optic5core5:
Thanks task

Too bad I can't post this in the devel thread which is so full of garbage.

Your work is appreciated task. This rom is amazing.

Confirmation: 64T70244KB067082P

Signed,

A Canadian user
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks dude. :highfive:

P.S- Not sure if you've noticed. But this thread is full of garbage also. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamFan05:
cLock widget not working on 4-3-13

Is anyone else having trouble with the cLock widget? The weather is not working on mine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dfg187:
X2.

Couldn't do a dirty flash either lol. Forgot to back up some of my shieettt haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No. You are the only one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Some of you that post here just amaze me at times. Please follow XDA Rules and search before posting. The cLock issue has been discussed just a page or two back. Please do your best not to clutter this thread with things that have already been beaten to death. We want the legitimate questions to be posted here for support. Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] badgcoupe:
Task, how does your ROM differ from the one posted over at aokp.co ?

Just curious what you are doing over the what I assume is the base D2ATT build.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You have two options to find out.

1.) Flash it and see..

2.) Look at source.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not really sure what you expected. There's no possible way for me to go through all of the changes/differences in this ROM form the official one. The most detailed change log would be in the source itself. That would be the articulate information you are looking for. You need to remind yourself that I was one of the first to post in the original thread and this ROM has been here for quite some time. There were only two ROM threads. Mine and CyanogeMods. Thats a long time and a ton of changes that would make a difference between this and official dude. I make source available for you all to see these types of things. You should utilize that. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
Is there a way to have camera rotate without having rotation setting on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Hey task, thought i'd ask this question here since it's more appropriate. Before going any further I understand that 3.4 is new and in development and you are pumping out updates that are fixing issues left and right which is great. On your phone the build is running flawlessly but all devices are not treated equal. With that said, my phone seems to hate 3.4. I've tried almost every 3.4 ROM out there and yours seems to perform the best on my device but it's still not without issues.

The ONLY issue I have is that my phone often crashes when it's locked. It never happens when the phone is in use but only when it's locked and usually screen off. It doesn't reboot to get a last_kmsg but the device becomes un responsive. I've been testing for a few days and the last few builds. I flashed your newest ROM yesterday and left it stock. installed my apps, rebooted and was good to go. Started listening to some music and not 5 mins in it just stopped, phone unresponsive. Rebooted and everything work great. Made it about another 5-6 hours when I was chatting on the device locking in between chats. Got a msg, went to unlock and nada. Just like that, phone was unresponsive again. it seems to happen EXTREMELY randomly which I understand makes it a nightmare to troubleshoot, also because you are not experiencing the issue.

I see you have some stuff going on fixing force closes but I wasn't sure if that would be the same issue i'm having. I'm leaning towards no and I'm in that small % of phones that don't like 3.4 yet for some undiscovered reason. I am patiently waiting and monitoring feedback from multiple sources because i don't think i'm the only one with the issue.

Has anyone else been discussing this type of issue with you? Have you seen any commits or anything from other devs that maybe fix it for a future release? Only asking because I realy enjoy your ROM and the features you've implemented but I need some stability so i'm back on 3.0 watching from the bleachers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Your issues can come from something else than the 3.4 kernel, like app or settings.

Did you try using different gov/scheduler?

Did you try running it without restoring your apps? (with just the Gapps)

And of course, the most important is to clean flash. Those 3 are the basics troubleshooting a user should make before coming in here. Now I'm not saying you didn't but you didn't mention you did, therefor, I simply assume.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
very understandable.

I've tried many different gov's/schedulers and combinations, none made a difference in the long run, same end result.

I haven't tried running with just gapps. Maybe next week i'll give that a try, i just use some apps very frequently so the weekend wouldn't be a good idea.

Always a clean flash. I can't even remember the last time i dirty flashed anything.

scratch that, i'm going to start fresh today so I can' gradually ad apps back during the week. making sure I download from the market.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shone1980:
My phone restarted during the call today. I am on latest build, wiped clean flash. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Revert to a build prior to the 3.4 kernel implementation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
When I try to play music on a music player it always force closes. Even when I try clearing cache or when I try installing new player always force closes .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thats sounds pretty cool. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Sounds like dirty flash to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
ota update

Ive been using your rom since day 1. With the past 3 releases I cant use ota update. when it loads cwm recovery it tells me marker is not found. and wont install. When i do a fresh wipe and install it works fine. Also cwm is up to date. so can anyone help please??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Give up and go to TWRP? Or make sure you're on the version of CWM that works with this (there's more than one out there, and they handle the scripts differently). IIRC, the most current version of CWM does not work (but I can't swear to it).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
To add to what alacrify said, get rid of CWM. It's crap compared to TWRP. (This is my opinion, there's no need to debate it here.) And if you were going to OTA anyway, why not just download the rom by opening up the thread in your browser?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
Ok i switched over to twrp. Ill see what happens next time I update. I was also under the impression if I download from thread I have to do a wipe then fresh install. Rather then ota looking for existing then updating???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Whether you ota or download from the thread it is the same file you download. Either way a full wipe is recommended. Dirty flashing the ota file is no different than dirty flashing the file from the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
Ok great thanks for the info. I was under the impression that ota was the right way to go. Doing a full wipe kind off sucks every 2-4 days lol. But tasks rom is worth it. thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I only full wipe on the weekends in general. However, if I haven't, I don't report any issues since I know it's my problem - instead I full wipe then if it bothers me enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Is service mode implemented into the ROM? Cause using the *#*#197328640#*#* combo goes to service mode but it only black screen with no functions except for "input" and "quit".

I just want to change my baseband to 850mhz to conserve battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merpius:
Unable to upgrade or install apps from store

I just totally wiped my phone (including internal storage) and flashed the latest. I did the total wipe because of this issue, but wiping did not eliminate it (surprisingly).

Whenever I try to upgrade and existing app (system or user) it fails, claiming that there is insufficient storage space available. If I uninstall the app and try to install it, it gives the same message. When I've tried to install new apps (with play store) it has worked fine. Restoring with Titanium Backup also works fine. Installing using Amazon App Store gives a message about insufficient storage.

Anyone have any idea what is going wrong here? Seems like the only consistent answers that I could find relating to the insufficient storage issue are actually having insufficient storage (I have GBs left still) and/or bad .odex files (but I couldn't find any .odex files).

EDIT: I found the issue was with link2sd; an app that lets you install apps to the sdcard (cool) but has a default setting (that it reverted to) that makes nothing work right.

Leaving this here as my badge of shame + so that people who get this message can find it in search
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JeRrYFaR:
So I just did a full wipe and installed 4/5 and tried yo setup exchange and it's telling me there's no certificates. Did I mess something up? How can I get the certificates needed?

I've used several versions of this ROM w/ no issues in the past.

EDIT:

I just rebooted and now it's working.. nm I guess.. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIowaKid:
For comedy sake, i have to highlight how funny this comment is if taken out of context by anyone other than habitual flashers like us. Does something smell in the office Karl?!?! Haha!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Bluetooth and Tethering

So what's the story with these two working on the new 4/5 build? Are they working correctly? The latest thread on these two was back in late january. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What are you talking about? The latest thread? I only have one thread and all the information necessary is kept there. I'm not sure what you mean by this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
Charging led doesn't seem to work for me. Clean flashed twice and both times it's just resets itself to off. Bummah...but not the end of the world.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
I ran a search for tethering and the last thread that came up in the search was back in January.

---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------

I think I worded it wrong. The latest post was back in January on tethering. So the latest build is today but there's nothing on wifi tethering working or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its probably because they both have worked since January.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
I thought about that but just wanted to make sure. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aew0314:
just did a full wipe and flashed aokp tonight, im having the same issue, when i go to the LED control settings to enable LED while charging (requires reboot) when i put it to on, it always goes right back to off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
So maybe you and the few others that have already reported the same thing before you can team up and fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aew0314:
i don't know what I'm doing, I'm just reporting the issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's understandable. But the issue has been reported multiple times already. Not quite sure I see the point in constant reports of the same bug? Do you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I just updated and the LED is working fine on mine