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

Can you point me in the right direction as to how I can adjust the intensity of haptic feedback? I'd like to have it around the intensity of stock TW. I know some basic smali stuff. I just don't know where to look lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I've already fixed it. Smali will do you no good here. You will need to wait for the next release whenever I get around to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Settings -> Device Options -> Haptic

(Work in progress as per update notes, which I'm guessing you didn't read)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AacidusX:
Tried to unlock my screen and it rebooted. This happened on two occasions.

Here is the the last_kmsg

http://db.tt/yPHKtsxY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Devhux:
Given that it's clearly mentioned in the change log in the first post that the feature isn't working yet, I'm not so sure task would have a better response for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What have you tried to fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Dam. Also having the gps issue with the latest update. It's not picking up a single satellite. Did a fresh install. Got the latest gapps from op as well. Tried using fix gps and gps app to reset the agps but nothing...

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is a development thread. Please use it as one. You've provided no information for the troubleshooting to begin. Also. This has been reported many times now. The only thing this is accomplishing at this point is creating clutter this thread. I've said this many, many times in this very thread. If an issue has already been reported. Then there's no need to continue beating the dead horse. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Worked for me earlier today mountain biking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AacidusX:
The first time it happened was during a dirty flash.

I then performed a full wipe by formatting everything.

Still occurred. No biggie, just reporting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. That's fine. But again. What have you tried to fix it?

READ THIS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
there has been some issues with the GPS on cyanogenmod too...

this all started when they included a new gps.conf file in the nightly rom.

since your rom is also using the exact same file, I suppose it might be related.

I just started using your rom... and I did not have any GPS problem so far. I'm using fastergps app to customize my gps.conf file. So this might be the reason why I don't have any problem. But before using your rom, I had Cyanogenmod installed... and I had some problem on the first gps fix after the upgrade with the newer gps.conf file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? What does this have to do with the post of mine that you quoted?

I've already started looking into it. It's not that gps-config.xml. Its a little more than that. Source is available for you to look at if you like.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@Everyone

I just wanted to let you guys know that I don't care about GPS. Please remember that before posting here anymore about it. :D :good:

P.S- I really do care about GPS... I just don't need the constant reports. It's already being looked into. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Those of us that have been around for a while know you care even if you say you don't... it's one of the things that makes us like you. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
FTFY :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
FTFYA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Fix for GPS Issue(tested and working for me):

1. Backup your existing ROM in Recovery - NAndroid Backup

2. Restore your old backup or install the last ROM which has GPS working

3. Enable Location and wait until you have GPS Lock on any App using the GPS, preferred Maps.

4. With GPS Lock on the app, Press the power button and reboot into recovery and restore to the backup done in Step 1.

5. Voilla you have the GPS working :)

Hope this eases the pressure on Task

Credit to the person who have posted this in TW Forum, think Venom was the man:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Nice! This actually worked for me

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

To all here the posting matrixzone made for a fix is a

good example

of how to properly contribute when there is an issue..... (see his post above)

He did some research...... he found another who had a possible fix.... he tried it and tested to see if it was good

......After he found it would work.........

He then shared it ... helped the

Dev

and gave credit to the one (

venom

) who originally came up with the fix......

This was an excellent posting...... Thanks !

~~~ oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unk2009:
I'm going to give this a go, thanks...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Verified x 2:cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Topic guys. Stay on topic. We don't need a million "I'm going to try this..." "It works for me too!" posts clogging up the thread. If it works for you, cool. If you are going to try it, cool. Lets keep to the development side of things please. Workarounds are definitely cool and all. But source fixes are even cooler in the long run. That's why this thread is here. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Just like to confirm I've gone 3 days without a random reboot and also since in disabled and stopped using AOKP Swipe ribbons. I noticed it did the reboot randomly when opening an app from the ribbon. I know still work in progress so I just disabled it.

using the quick settings ribbon I have 3 set but I don't see them anywhere.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I use ribbons everyday and do not see the issue. I doubt that is why you were having problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Yeah ribbons are acting funky on me. I've done 3 clean wipes(one was update to 4/26) I tried cloning my notifications ribbons setup and use it for Quick settings ribboms and any time I opened Notification Ribbons ROM Control FC'd. I wiped and that fixes it, I didn't try to clone again. However like I said my Quick Settings Ribbons don't show up, modifying my notification ribbons does not work, i f I change or add an app and save it, the settings don't save.

I didn't report any of this because it's a new feature and you mentioned it as being a WIP and have possible bugs.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
With everything working as good as it does its not really much of a work in progress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
Can anyone check and tell me if the mobile network settings are working for them? Every time I set a preferred network type, the setting automatically goes back to what it was. Also when I toggle usage of 2g only, the selection goes blank.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Use the Q & A. This is a development thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Hit "network operators"

Let it find them and pick at&t

Done. Now try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
It just" searches" indefinitely!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Excuse since I haven't been here in awhile, switched to the Note 2, but Task are you getting the s4? I love your AOKP and was wondering if you were gonna bring us the amazing rom to the s4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I pm'd u. It will find it eventually. Let's get out of this thread. Not related
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is a development thread for this ROM. Please stay on topic. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
If you had searched the thread, you would already know the answer to that question as Task has made his feelings known about that several times now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dennis0201:
I've read the OP but don't know how to update google search via playstore. There is no option for update only open when I browse on playstore. Sorry if I miss something.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
you need to download the gapps in the OP and try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Lol like I said they are acting weird for me. Some how the ribbons just showed up in my quick settings. I'm gonna give the swipe ribbons a chance again see if random reboots restart.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] desichiko23:
Is there a settings for home screens? Like u can choose how many screens u want and which one to be home screen??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Not on the default launcher. Use an custom one, such as Nova which is packaged with the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
...And post this stuff in the Q&A thread, not development!

[Edit] how many times do mods and other members have to repeat this? I bet almost half this thread is just that. With almost 300 posts, you should know better dude ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wickidmasshole:
If you Uninstall it with titanium backup then install again through the play store it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Even if he does this, he will end up having to do it every time he flashes this ROM and gapps. I've already posted here and in the Q & A thread that everyone needs to redownload the gapps package from the OP again to avoid having to do this every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I just had an evil thought...when you update the ROM (or kernel, or Gapps) update the OP and the thread title, and don't post in the thread. It will get spoiled by people who find it posting responses at the end of the thread, but it will make people F5 the OP and READ it.

Just a fun thought :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wireratt:
I didnt think he would be without for long.

Super smooth rom btw task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
Could do that and just lock the thread for a week.... Make people learn to read the OP and Search for answers that have already been posted a hundred times on their own :D - Hows that for an evil thought? lol

Could also add a script in the flashable ROM zip that automatically fully wipes the device before it flashes the ROM - eliminating all these "I dirty flashed and now this doesn't work" posts....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SRTGS300:
After being on Task650 since my GSII all I have to say is, its stupid how stable and smooth this ROM is . I dont have not one complaint other than an awesome beats issue but its not a dealbreaker like some of the problems ive had with other ROM's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Task's post specifically says that you should be able to flash a new version of the ROM without fully wiping the device. That would also kind of defeat the purpose of the OTA updater, no?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No it wouldn't. Even if the full wipe script was put in place it wouldn't defeat the purpose of the OTA considering you would still be updated to the latest. The only thing it would defeat would be most of the issues that users have from not fully wiping. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
It actually says "wipe data/factory reset, wipe dalvik cache, wipe cache, and wipe /system" - after you first make a nandroid backup... Maybe you should actually read the entire OP. ;) :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ErebusRaze:
Thanks yet again for an amazing ROM. If only we had your unparalleled intellect and wisdom on the GS4 side. But, alas, we are forsaken and left in a lonely dark ruin of locked bootloader misery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] photolarry:
youmail settings

if you go into phone settings by pressing the phone key then settings from menu... there is an option if you scroll down for call forwarding... then you can verify it reads: 14158256503 for California. I'm pretty sure it's set on the SIM so if you flash new Rom is still there as confirmed since I'm flashing lots. Should not matter which carrier. I'm using T-Mobile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? This has nothing to do with this ROM. Please post in a more appropriate thread please. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Just to clarify, it's still okay to flash a new version of the ROM without completely wiping the device per the instructions in the opening post then? Obviously if I have any issues I'll need to perform a full wipe and verify if the issue still exists before I post anything. I know in the past Task has mentioned that it isn't possible to just "update" and a full wipe must be performed (For the 3.4 kernel update, I believe).

That being said, I have been "dirty flashing" as I understand it for the previous few updates and haven't had any issues at all, save for the Google Now one that you posted a fix for. It's been super stable and smooth for the past few updates, even with a minor overclock (1.7 GHz). :o

I did read the whole thing. It also says this in parentheses after those instructions... which is why I posted:

Either way I suppose it doesn't matter. Some people will probably lie and say they fully wiped yet post issues anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's no need for any clarification. Just follow the installation instructions that are in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Can I ask what the purpose of "(If already on AOKP 4.2.2 you should be able to just wipe cache & dalvik." is then? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All you need to do is read it and I'm sure you will figure out the purpose. Its actually pretty simple.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HAVOK83:
Because we don't want you coming back here complaining of issues because you didn't fully wipe. Come on brah if you're flashing custom roms you must know it's always recommended to fully wipe to avoid any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Come on man lay off. Fully wiping adds an extra 5 seconds to the flashing process. Who has time for that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
Task,

Here are the questions I read per your OP. I read the whole thing before I began. Hypothetically, let's say I'm currently on a previous Task650 AOKP 4.2.2 release.

Here is my understanding of the steps and the actions I would take after reading your instructions:

I have the latest CWM recovery

I made an Nandroid

I booted into recovery mode

I skip to step 7 since I already am on a Task650 4.2.2 release

Wipe data / factory reset

Wipe system partition

Wipe cache and dalvik cache

Flash ROM

Flash Gapps

Reboot

If I have issues, boot into recovery and start at step 5

All I'm asking for is a simple yes or no if this is the correct interpretation of the instructions. I have read your instructions several times and I'm asking for clarification because what was posted in the last page completely contradicts what I understand from your instructions.

If this isn't what you're saying and you do want users to ALWAYS fully wipe when they flash your ROM... why include a sentence that says not to?

Read the last page before you make accusations that I did not fully wipe my device or that I'm even posting an issue. It's not even what I'm discussing here...

Restoring your apps, data, system settings, MMS/SMS, and other customizations most certainly does not take an extra 5 seconds. With a new release coming out every few days, it becomes rather tedious to do this every time, even with Titanium Backup Pro. Is there a secret method of restoring these that I'm missing here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sorry dude. But this is not a "How To" thread. This is a development thread. Please follow the rules and read the OP before posting here. You are definitely posting in the wrong thread. The instructions are there. Just use them. If you don't, then don't. Just don't expect support here if that's the case.

Just do this if you want to flash this ROM:

Make sure you have CWM or TWRP Recovery

MAKE A NANDROID

Boot into recovery

Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system (if using CWM). To format system w/TWRP, select Wipe then System!!!(If already on AOKP 4.2.2 you should be able to just wipe cache & dalvik. If you have ANY ISSUES, FULLY WIPE BEFORE POSTING IN THIS THREAD!!!)

Flash ROM

Flash Gapps (Use the gapps package that I provide in this thread!)

Reboot

P.S- Just being honest. But I don't care how long it takes you guys to setup your devices. I can guarantee that I put waaaaaaay more time into this ROM for you guys to use. There should be no issue at all in taking 15 minutes to an hour on your side to setup if you need to.

P.P.S- I'm going to shut this thread down now for a little while so that it doesn't get further derailed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
agree with task, you shuld only put a link for your profile of the page you are hosting your builds. and close the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Works for me - just tried it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Excellent release...

BTW, my camera, toggle flash, all calling, rotate on video, and sms working... my steps have always been to fullwipe, immediately flash ktoonsez kernal only rebooting recovery, appending both OP instructions together, minus the nandroid, never using tibu for anything...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
I took another logcat log without restricting it to E or greater. However, there is still no thrown exception :/

FYI - clean install 7/28 (wiped cache/dalvik), installed latest gapps. left with default F***You kernel as well.

Also, if you want to give me a more proper way to logcat, I want to help out as much as I can, so tell me what to do :D. There are multiple camera tags, so I don't know which one the error is coming from.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Seems to work fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Same for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ottawadad34:
Great rom. Have no problems as of yet. Will post any bugs that have not been addressed if I see any. Again thanks for all your hard work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goronok:
Its a CM update that hosed camera - cyanogens build is having the same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk2rocco:
Fantastic! I'm gonna be running thing as my everyday rom so I can report on any problems I find. Really Great job on this thing :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradyonly:
I'm not currently on aokp's, but I noticed its when the flashlight toggle is turned to high that it doesn't work. Low works fine and more than bright enough to get me through the dark. Scroll to the bottom in the notification drawer settings to flashlight mode or something along those lines
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cpu999:
The navbar doesn't show up when you turn it on.

Does anyone else have he same problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Did you even bother to read the changelog in the OP????

AOKP Jellybean Build 7.28.2012

Theme Manager Added

Updated Kernel

Updated SuperUser.apk to SuperSU.apk (It works better)

Updated to latest NovaLauncher.apk

More RomControl Settings added (If they don't work. Remind yourself that this is a preview. Things still have to be worked on.

A ton of behind the scenes fixed. (Check out CM and AOKP Gerrit)

Underwear
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slomanski:
I found I can use the camera a lot with no issues and then all of a sudden it freezes. The last time I pressed back a few times and got a message saying that Gallery was not responding and do I want to close it. I closed it. As with the last build the camera is no longer accessible without a reboot unfortunately. Will continue testing and report on anything else I see on this great preview. Seems really fluid and smooth on the whole though. Enjoying my first outings with Jellybean. Thanks for all your hard work on this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Task update works awesome no issues :)

I'm very happy with the switch to superSU I've always liked it better:D. And theme support is great. Rocking cobalt again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
urr.. Delete, not the QA thread.. opps.. sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Wow. All i can say. This is the smoothest build yet. thanks task and ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Vondis:
Google Now on the lock screen and themes are back!!!! You guys rule. No issues to report. It's butter baby!!:good::highfive::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhinez:
This ROM is great! Outstanding battery life! Thanks Task. BTW, I'm using the kernel provided with the ROM.

Edit: This is with Preview build 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
google now has always been part of the lockscreen. you can also hold the menu button to bring it up. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Vondis:
Huh I guess I didn't pay close enough attention before.:o Thanks again sir!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Yeah up in lock screen:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If I close this thread, I will stop posting builds publicly. There would be no reason for me to post builds at that point with a closed thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
I hope this doesn't happen. Loving all the awesome features you are cramming in this bad boy. I'm happy with even monthly updates, just not a permanent shutdown of the best and most viewed thread in the GS3 section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Me either. Awesome ROM!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
People just need to learn to respect the development thread as it is just that. That post the other day about clarifying if you can dirty flash I felt was someone purposely trying to get under the skin of tasks. It had nothing to do with the development of this rom and was just a complete waste of time. People need to learn that you don't HAVE to post in this thread to follow it. If you have nothing development related, simply don't post. There's nothing wrong with that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Right. I only post if I have something to say.

(See what I did here dudes... this is an example of what NOT to post... that is actually my reason for posting it. I think we can all agree that I shouldn't have...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Just an FYI for the future, Task doesn't really appreciate +1 / "me too, me too" posts. They just add clutter to the thread.