yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pgonza02:
Yes, Task, I've been following your threads long enough to know that I need to wipe the device many times before I even consider posting a question. I have done that, and the issue is still there.

The LED is not a big deal, like I said before, I never really used it and was just trying to add more information to a problem that someone else was having.

On a second note, just to be clear, are you saying that there is no much you will do if you don't see the problem yourself and a few posts later you say that you rarely use Bluetooth? So following that logic, we should stand to conclude that you will probably not see the problem, therefore, you won't do much about it?

I know there are lots of posts in this thread that are a waste of time and can be easily addressed by being deleted and have the user read the FAQs, but there is a community here trying to help by using the software, as recommended, and testing different scenarios that you cannot possibly, nor would any reasonable person ever expect you to, be able to consider or run through.

You do an excellent job, most of it un-appreciated and there are many of us here that are willing to help iron out the problems that will come up, specially with how quickly you turn around your releases. Getting into a discussion with someone about whether or not something belongs here or not, whether it's in the FAQ or not, is pointless. If it's irrelevant, delete the post. If it is relevant and you are working on it, just mention it and the people who value your work will respect that, if you haven't seen the issue and need or want more details, feel free to ask, we will provide it and also try to narrow down the problem.

Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Has anyone noticed lag issues when gaming? I start up a game and it instantly becomes laggy and i have to reboot to fix the issue. (happens when you start a game again) fresh installed, using stock kernel & noticed this with multiple governors too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n023b:
Hey I bought a phone and it was rooted and flashed with this rom...When I go into AOKP OTA updater it says "d2att (4.2.1 jop40d) build 1.1.2013 available, download it?" My question is can I just download and install or do I have to do something else first?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Thanks for this masterpiece Task!

Flashed dirty (yep,lazy!), using Kt kernel 1.1 and running flawlessly!

You're the man! :thumbup::)

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
I can provide these all day long.

Logcat of the bluetooth issue. It happens for 5-10 seconds before the pause.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vic_singh:
This Rom will make your phone runs smoother, faster and not sure if it's just me but it also seems like it have better battery life.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
can we use the underwear kernal with CM 10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
1) Why?!

2) Test it yourself. Your question does not belong in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Refer to my post above. ;)

It will probably the last thing i look at as it stands for now. I have what i think are more important things to work out first. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I was pretty clear about where i stand with Bluetooth. I don't use it so i don't really care about it at this point . I have what i consider to be more important things to work on. You have to remember that i build these ROMs first and foremost for myself. Then i share them here on XDA. so when i think i need to work on something first, i do just that. So in a sense, yes. I don't use Bluetooth so i wont see the issues, so it doesn't bother me. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
That sucks for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrMarkEdward:
Just wanna say Task ty sir for sharing your rom with us it is very much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
2char delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
U should be able to simply lock then unlock, happens to me too, I think its a cm 10.1 thing period. But try just lock n unlock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] torontomark:
Task, I am writing this in the most understanding manner as we very much appreciate your sharing your ROM with us.

For most of us, we are waiting for you to make the next big improvement and we cheer you on with the rapid developments you provide us with. I think that we are not able to comprehend at times how some issues are not as important as others.

We are with you on this journey as spectators, contributors and as supporters. I think this is why we sometimes push for things that may not seem to be in the same order as your punch list.

With respect to the Bluetooth issue, the ones that need it, like myself are requiring this as we are, by law needing the Bluetooth to be able to talk while driving. Ontario police will issue $150 tickets if we are caught using the phone in our hand. Music streaming, while nice is secondary to the actual "development" as we could just plug into the headphone jack.

We are interested to know since the original 4.2.1 release had no discernible noise or issue while the prior release to the current had a bit of static. This last release somehow developed this affliction. My experience with it was bad enough that it caused the phone to lock up and I had to reboot the phone.

I guess since this is not at the top of your list, then please comment on whether you think that it is more appropriate for some to wait for the next one, or should we tell those people that its too difficult to tell and they should pick something else to run on their phone. This makes it free for you to not have to address this issue continuously.

Respectfully :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
This ROM is like my cigerette addiction. No matter what I do,I keep coming back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Running through my flipboard app on AndroidNews and I ran across this, purdy tight! That damn unicorn is catching on man, going viral!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's really no answer to this. People can wait for the next one if they want to, but Bluetooth could or could not have been worked on by then. There are tons of ROMs out here and anyone at any point in time can go and flash whatever they choose at any point in time. There's really no need to relay that to anyone considering that's just the fact of the matter. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its only for the nexus line. Has nothing to do with this device. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Yeah, I know ....just sharing something I thought was cool. That's all man...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] biofilter69:
I can confirm this also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krayziepop:
Task, I've spent a good hour trying to recreate and capture this weird Bluetooth phenomenon, and I think I have it finally. I understand if BT is your last priority, but I also know that without a logcat you'll never really be able to see whats going on. I have that logcat here, and you are free to do as you please with it. I am loving the ROM so far as it is, and I sincerely look forward to its future. Thanks for sharing this with us - this device just wouldn't be as phenomenal without your development.

The music glitches and speeds up at around 1:31:37 and continues until the end of the file.

I am using your latest 1/1 release with KT's kernal of the same date. I realize its not what you provide in the OP, but I get the exact same results with either. My governor was set to performance to eliminate the zillion lines of hotplugging messages and I used the new ROW io scheduler. FWIW - I get the same results with the stock underwear kernel of which you provide using bfq and on demand.

I hope it helps in some way. Take care and God Bless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ava0425:
Those worrying about Bluetooth being fixed, the cm kernel will get updated with the fix eventually. Pretty sure the CM10.1 nightlys have the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm actually not looking into anything Bluetooth right now. I've said this a few times now. Sorry.

I have some more important things that i need to focus on right now. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marksterbate:
Extremely happy with this rom, thanks task and everyone else involved, I'll fork out some Christmas money once I get home :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krayziepop:
No problem. I just wanted to make sure it was well documented anyway. I spent some time looking through the logcat myself and seen there are several things in the ALSA layer that are not playing well with the hardware. I don't think it will take long to iron out, and I would guess somebody on the AOKP team is already working on a commit to resolve this issue.

Development seems to be moving along well now anyway from what I can see in the Gerrit, I believe there's lots more in store for us in the near future. In a month or 2, these current issues should all be a thing of the past. :thumbup:

Thanks again for your time and hard work! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. I'm sure it'll get worked out eventually. This is just a new OS so these things have to get some work done to them. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Found some other posts on tethering, sorry for the clutter task. Deleting my other post now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
This issue will most likely be fixed by some commit in the near future and incorporated into the ROM when it is... I hope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
I also experienced this. I ran pegasus on the last build fine but as soon as i switched from interactive to pegasus my phone locked up and rebooted. I usually use ktoonesz kernel but since 4.2 i have been on tasks kernel with excellent battery life and performance.... Just the pegasus thing only bug i found haven't made a phone call yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prosparky:
Excellent work as always,Task!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
Problem is bluetooth is broken all the way back to 12/6 in the 4.1.2. (Upstream qcom merges)

Then you run into a bunch of other bugs with the phone that make it unsuable.

Stock drains the battery way too much for usage. Some of us are proper fuxxed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
Seems like you're screwed can't use stock cause of battery issues and aokp because of bt crazy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
The previous build was working perfectly with bluetooth. Just revert back to that build, but don't expect to get any support here if you run into any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbrummell:
Exactly why I went back to stock Rogers ROM, rooted, de-bloated and running KT's kernel. And it plays much nicer with the network around here. With no BT fix in sight from the AOKP team, it just made sense. Sucks though, I've always ran the latest/greatest ROM's since I started with Android back at 1.5, now with this phone I can't. It's just not usable in that state.

Always watching the thread for a fix though. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Vondis:
All you bluetooth people need to realize that this ROM is something Task made for himself (meaning what he likes and needs) and then decided to share his personal creation with everyone for free. He will continue to improve this ROM based on what he wants and needs because thats who he originally created it for. He didn't create this for anyone but himself. We are just lucky enough to also use what he uses, again, for free.

As for driving in a car afraid of getting a ticket, I have this amazing option called speaker phone. Works wonders. Complaining about a feature he doesn't care for or need is a waste of everyone's time. This applies to more than the bluetooth people but right now you are the ones whining the most.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
Actually, we just discovered that this is low on the list last night.

Bluetooth was basically ignored in this thread and never got a response.

Now that task has expressed that bluetooth is the last issue on his mind, I will not be bringing it up anymore in this thread.

Communication is a wonderful thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Interesting that you think it is this particular phone given the lack of issues with stock ROMs on it. As you note, BT for you is not an option. For me, LED notifications are not an option. If I was one of the those obsessive-compulsive check the phone every couple of minutes people, it might not matter, but I'm not, so knowing if e-mail, text or missed call exists requires color-coded LED alerts.

For most phone customers, having working, reliable ROM is a reasonable expectation, which is why stock ROMs are thoroughly tested before release, including updates. I'm sticking with Task ROM because I have what I need for now and it's so much faster -- but I may not update every time there's a new build unless I can simply do so without wiping, just like stock ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
I wipe cache and dalvik cache and never have an issue. Now, if something seems to be an issue, then I'll do a complete wipe. But otherwise I don't bother. Of course, I always nandroid backup.

The problem is that people can't follow directions or need their hands held. Those folks either need to search or leave your phone's stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
question

I was running this rom had it working great,even had google wallet working,eveything was good except know bugs,i had let my daughter and 4 friends sleep over i left my phone charging on the counter, woke up and it was sitting in a puddle of water smoking cause it was still plugged in charging, so they were messing around in the kitchen late at night and ruined my phone, so i have a new one on the way my question is i have backups on my external card witch is still good will i be able to use those backups on a new phone with a new IMEI,i know this might not be the place to ask i havent posted once in here cause i do read the OP and all my problems were mentioned,or i searched and found my answers, but i trust the people that post in here specially task, hopefully this doesnt cause a problem thanks if u can help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
What the hell is everyone taking about BT? Try different things and see what works. I'm running AOKP 1/1 with ktkerenel 1/1 and BT works prefect. No cutting in and out, no scratchy noise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
While it could possibly work and be fine I wouldn't do it. It would probably cause more problems than it would be worth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
So wiping cache leaves apps and data alone, right? I don't see dalvik cache on CWM recovery. In fact, I've long been mystified by the consistent advice to wipe dalvik but not seeing this option in recovery or download modes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
You have to look under advanced and you will find davlik cache. Wiping the caches does not remove apps.

Sent from my Wicked SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
To answer your question, if you backed them up with Titanium then you should be able to restore them on a new phone also with Titanium - However, this question/answer string would be better targeted at the General Q&A forum... as all questions here should be ROM related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
been running this baby since day 1 and haven't found any problem yet, I don't use BT so don't even know how that is. but everything is smooth,fast and batter amazing.

Great Job TASK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
I agree. I just did a complete internal SD format(to fix the "0 folder" issues), and wiped EVERYTHING, installed this ROM and the only issues I can see are the call and sound quality issues Task already knows about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
I cant even notice anything on call regarding sound quality
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colhavoc:
Been having the same issues with 1/1 with my Bluetooth speaker (happens all the time) and headset on my car (only occasionally). Glad to see its not just me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
The 0 folder is not an issue. Simply cut and paste your stuff into 0/ and never look back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
That's weird. I noticed it on my first call I made yesterday but READING THE CHANGELOG, I knew it was something he knew about. I also noticed last night when I had my volume on full, the ring tone choices and other sounds had a tinny sound to them. I assumed it was related to the call quality sound and it just needed to have the gain adjusted or something like that.

---------- Post added at 11:20 AM ---------- Previous post was at 11:17 AM ----------

I agree that it's not an issue but after a while, my internal SD card got cluttered with junk that I didn't use anymore so the complete internal format was my personal choice. I could have moved the 0 folder, but I wanted to start with a clean phone anyway.

The point of me bringing that up here was to demonstrate that a clean install yields far fewer problems, my point wasn't to discuss the 0 folder issue in this thread. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
first of all i never mentioned anything about titanium backup i dont even use that,second it is a rom related question because i backed up this rom with twrp onto my external sd card,and how is someone in the general Q&A gonna answer a question about tasks rom,and it doesnt look like your a forum moderator so let task tell me to post somewhere else,i will end up doing a fresh install because of the newest version task released but i wanted to know if thats even possible to back up a new phone with a backup from a old phone with tasks rom,and ive never seen this asked in the 2000 pages of posts in this thread,it is a general question but general to tasks rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yze:
this is in no way related to this thread. this is a development thread.. which is why you were told to probably ask for help in the Q&A thread about the backup question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
hey does anyone else notice this little bug? I can't seem to get the fast charge statusbar toggle in my notifications. although its enabled, it seems to be the only toggle that doesn't show... I had it before the 1/1/2013 release though .. so strange
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
Despite your ridiculously argumentative state, I'll ask another question in attempts at helping(and the question isn't "why did you trust your phone around a bunch of girls")... but if you backed it up with TWRP(again, not related to this ROM), then wouldn't TWRP have the ability to restore it as well? Basically the EXACT same question I asked originally, just replace "Titanium" with "TWRP".

The point I'm trying to make is that YES it's related to Task's ROM, but the backup/restore abilities OF his ROM you're asking about AREN'T. Maybe the question would be better suited for a TWRP thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r_scotter:
Look at the OP and you'll see a link to the Q&A for this rom. Although your question was rom related, it isn't development related. There's lots of good stuff in the Q&A thread and Task posts in there also. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
I even went one step further and suggested he ask in the TWRP thread once he gave the information that TWRP did the backup. Despite me saying "Go somewhere else", I meant it in the sense of trying to actually help him find an answer to his question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
it's not general to task's ROM - backup/restore is based on what recovery you use. if you don't want to ask in the Q&A section then it would be best asked in the thread for which recovery you are using (TWRP, CWM, etc)...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This is definitely not a general question about my rom. It a question about a backup that was made with a recovery that I or this rom has nothing to do with.

2.) This would be something to either ask in the recovery thread where you downloaded the recovery from or the Q & A section.

3.) If you don't like something that someone has to say, just leave it alone and wait for the nex reply. There is no need to defend yourself in this thread considering that kinda stuff doesn't belong here. I don't want the bullsh$t to pollute this thread again. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@Everyone

There's no need for 8 million people to jump on a question that some has asked here that they feel doesn't belong. Once you see someone answer it, it's pointless for the rest to jump in. Move along please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgruberman:
I didn't have this before but in attempts to answer your question, I added it and was unable to see it show up also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its not a bug. Its not even an option for this ROM. I would have to add fast charging to the kernel for it to even work. So it would be pointless for it to show when selected either way. You would have to use a kernel with that option (like ktoonsez's kernel) and if your using that kernel you would be using the ktweaker app to select that option. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pgonza02:
+1 that I see the same behavior of the toggle being selectable but not showing up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
-10000000

Please read posts before responding to avoid unnecessary clutter. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
You must be doing it wrong :p

PM me if you want help, x10user
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's nothing wrong. It wont work either way just as I stated before. It has to be included in the kernel which it's not so it's just a pointless toggle at this point. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Oh no task is right, i had it before because i was using ktkernel, but now im with the underwear kernel so it makes sense :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I'm getting some strange behavior from the touch screen. It is not registering some key presses and scrolling is problematic. It appears to freeze for a very brief moment and will sometimes scroll the opposite direction. I vaguely remember someone mentioning this. Is this a bug or some setting I need to change?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Never seen it happen. Did you follow the installation instructions and fully wipe your device? I would do it again and reflash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dalewest:
I don't recall Task ever being wrong about any aspect of his ROM. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Yes sir I did. I hate how you have to flash more than once for it to be right. Are there just inherent issues with CWM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its just how it goes sometimes.