yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Will this help with sound issues?

http://review.cyanogenmod.org/#/c/37261/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not when I already see every single commit that gets uploaded. Ive already merged it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
I don't like when Daddy drinks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minuteZERO:
Already merged a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eMadman:
Google Now is broken

I'm no longer able to run Google Now after the most recent update. I'm on the latest Task650, GAPPS, and Ktoonsez kernel.

So far, I've done a cache/dalvik wipe and a fix permissions. I have also tried clearing app data for Google Search.

So far, no luck. Before I go through the trouble of restoring, has anyone run into this issue? If so, have you found a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It works just fine and as it should. It's a Google Play Store app so you might want to look there and see if you need to update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available for download in the OP or just check your OTA Updaters.

AOKP 4.2.2 Jellybean 5.9.2013

Updated Kernel (Lots of code added from codeaurora)

Fixed all headphone issues

Update mGerrit

There's a few more things...who cares...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Thanks!!! 53P2102947863343U
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

On Topic People...... Stay on topic Stay to posting development related issues..... Post respectfully, or do not post.......

The development thread is for Trouble shooting issues or trying to resolve bugs....

IF you have questions then post those in the sister Q&A thread

If you have something personal to say or complain about PM us, the moderators and we will address ..... do not post personal diatribe or Q&A's here

Thanks ~~~ oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Task...Thanks...best build yet!!! Nuff said!

18K32454031246322
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shawn0223:
Hey Task,

Just had a random reboot with the phone just sitting at my desk while at work. Latest release, clean install. It was running interactive/ deadline for the governor. I've switched it to row for now as thats worked well on my device in the past. Attached the last kmsg for you to look at whenever you get a chance.

http://db.tt/wX9Qq1nh

Let me know if you see anything interesting or if you need any other info.

Thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I flashed 7/28 a few hours ago but twice I've locked the screen and then tried to unlock and it just wouldn't go on and I had to pop the battery. Has anyone else had the same issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Q&A. FULL WIPE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
Me... Back on ics aokp, it performs better anyway. Were you running ktoonsez kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Yeah, I am running ktoonz' kernel. I'm thinking about going back to ICS too just because I miss all the ROM control options :'(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I didn't think it belonged in Q&A because I was really reporting a bug more than I was asking a question. And I full wiped. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
opinions dont belong here. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
if you are running Ktoonsez's kernel then this wouldn't be the place to post. you would need to post in that respective kernel thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
It's funny people can post stupid crap like underwear but not an issue That could be rom related. I think this has been taken to an extreme. But it's your thread... My opinion is garbage anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Just thought I would report that haptic feedback is acting weird again. It was fine on 7/26 build, but now it's acting funny. Sometimes the physical buttons will vibrate twice or hardly vibrate at all, and all of the keys on the keyboard feel like they have different vibration durations. It feels really weird to type so I just turned off haptic feedback.

Not really a big deal at all. Seems you have an awesome ROM here task Very smooth! Great battery life! Great EVERYTHING! Thanks man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
O yeah we wouldn't have known it was the kernel if I didn't ask the guy. Please delete all our posts since we figured it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
My advice to others regarding bug reports:

If you find a bug, see if you can reproduce it.

If you can, post the steps (and maybe a logcat along with it).

Otherwise, keep it to yourself or ask about it in the dedicated Q&A Thread.

if(bugIsFound())
if(canBeReproduced()){
postSteps();
if(logcatPresent()) postLogcat();
}else STFU();
else STFU();

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
i was pretty sure you would understand that comparing two different OS's and saying that one performs better than the other is waaaay different then posting something as ridiculous as underwear.

Where is the proof that one performs better than the other? I think that's a pretty bold statement.

Having fun and joking around is part of this thread. Why is that so hard for people to figure out? Why is that line so complicated? It still boggles my mind considering the fact that it works in other threads. It's pretty much ridiculous in my opinion. We have a Q & A. We have this development thread to post bugs. And in between those bug posts, there's really nothing more to do than BS with eachother. And by the way. I think we've only had 2 bug reports with logcats to help us work them out. So most all of this thread should be BS. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
yep. we're looking into this. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Sweet! Thanks task, you da man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
exactly. and that is a very good reason why its so hard for us to figure things out. it seems that most people refuse to give the proper amount of info for us to even begin to help. we have to guess all day long. not sure why people want to give the least amount of info possible. it's almost as if they don't want help. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
this right here is perfect. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
I had the issue and didn't care because I knew it was probably the kernel but I wanted to let the guys know he wasn't the only one with the issue. Hopefully he either flashes cm10 aokp again or goes back to ur ics aokp because there is nothing else worth running on a galaxy s3 (or galaxy s2) now that's a fact right? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
its an opinion that i can actually agree with :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I see what you did there ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I apologize for my carelessness, kind sir. Keep up the good work :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please read the OP before posting here and post all questions in the Q & A. Thanks.

P.S- This is a development thread as you can see. I'm not a mind reader that can telepathically jump into your device to find out whats wrong. Not sure what you want me to do considering you've given absolutely no information at all. If you want help, you need to give information. Saying "my phone is doing things, please help" doesn't work out so well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Why are you guys doing this here? This is a development thread. Is it really that important for you guys to argue back and forth about things that are meaningless to this threads purpose? Is it really that hard for you guys to pm each other with these posts if you really feel the desperate need to do so? Please stop. You're only hindering the process here. Please just chill out and stay on topic. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available in the OP for download or just check your OTA Updaters.

AOKP 4.2.2 Jellybean 5.14.2013

Updated Kernel (Linux 3.4.45 and a ton of other commits)

Updated Blacklist Features

Updated Dark UI

Toggle Updates

Updated mGerrit

Camera Updates (Fixed Panorama Preview size, ect...)

Fixed StayAwake Toggle (Avoid Loss of User Setting)

Fixed Audio continuing to play even if paused manually

Added WirelessADB Toggle

Updated Ribbons

Fixed some leaks in VfyBasicBlock & BitVector

More...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Why is it every time I come to look at this thread I feel like I am entering a Pre-K class room? I swear It would serve everyone right if Task hid the DL link and made everyone jump threw a ton of hoops to find the link and then answer questions about what is in the OP to get to the DL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Devhux:
....Maybe this could help lighten the mood. :)

Thanks a lot task650 for indirectly helping to embarrass me on a Google+ Hangout On-Air. :D

No, he wasn't part of the on-air, but on the show we got talking about the AOKP unicorn logo, and I decided to show off the bootup logo. Of course, there just so happens to be the underwear kernel image first (that I forgot about). OOPS!!!!!

....Needless to say, we sure had a good laugh about that! I am still loving the ROM though so all is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
You should make this thread where you can read every post before posting and approving the ones that are acceptable to read on the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Nothing against your suggestion because I know you mean well but actually he shouldn't have too and no one should.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Slayer809:
Hello,

I installed this ROM and is really nice and fast, every is perfect but I have one question.

There any way where I can can have all the options of the sensors????? like the stock rom.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niksha:
very very quiet here lately

Only 9 posts in 12 hours?Either this is a perfect rom or people are crap scared to comment in case they get blasted ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Or I cleaned up the thread of pointless posts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You did a ton of cleaning. Thanks man. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
No prob man. I was tempted to remove 98% of the posts but didnt want to kill any useful info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
When you click on "Gallery" is it supposed to go to the camera first? When you hit 'back' it goes to the gallery.

I looked around and there doesn't seem to be any report of this so maybe it's supposed to happen? Any way to turn it off and have it actually go to gallery when you choose "Gallery?"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
This is a great question for the q@a thread... and just fyi, gallery is working fine here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Got my first ever random reboots in months, even with the 3.4 kernel.

I had two last_kmsg files but accidentally overwrote the first one on my sdcard *face palm*

Here's the latest one: http://db.tt/ktiTBQo5

Sent from my Galaxy S3

Edit: Some more info... My phone was in my pocket so I don't really know what happened. I only knew it rebooted because of the notification from Trickster Mod telling me my settings were applied. I am using interactive and row. My min is set to 389, and my max is 1026. Voltages were untouched, however, as of this post, I have upped them all by 25 since that's usually what you tell people with reboots. Let me know about anything else!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hampsterblade:
The link for Google apps is broken

Edit: didn't notice the mirror. Mod please delete this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
task650 sgs3 rom thread op captcha would do it. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Well, it happened again, even with voltages upped. This time I saw it happen. Picked up my phone to read a text, swiped to unlock, and reboot.

https://www.dropbox.com/s/bybgfmskflftc4t/last_kmsg 2013-05-15

Anyone got any ideas? :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mauer1:
I can not get nav ring to work. I'm assuming it works like Pie? I've searched on how to use navring but no luck so far. Any help would be appreciated. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Here's your help.

1.) Read the OP before posting here.

2.) There is a link conveniently located in the OP for questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mauer1:
Wow that literally took my way to long to find the FAQ and Q and A links. Having the picture right above the links makes me want to scroll through the picture...which scrolls through the links. Change the color to red and they will really pop. I'm reading the Q and A now...i guess you can clean up this post too. sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Looks fine to me on both the app and browser. It is even bright red and bold on the app. They are pretty bold as it is.

sent from my AT&T SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
I think the real issue is him scrolling past those hotties. I mean task provides u with everything u need... A rom... A faq a q/a and some boobs and u scroll. How dare you.

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itrunner:
Hey gang, i'm running the may 9th build at the moment, things are working great, except every now and then i'll lose my data connection. If i go into any of my apps (facebook / gmail / weather etc..) it'll show 'no internet connection'. thus far i'll reboot the phone and it's all good. I'm pretty new to all of this, but this is what i've checked so far.

- flashed the latest modem file (i'm on Bell Canada)

- confirmed correct APN, also confirmed APN settings with a different stock phone

- permissions repair within Rom Manager

- flashed to new version (i had this same problem on the april releases as well).

I'm not sure how to troubleshoot this one, but i'll gladly give any info that might help troubleshoot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Previous releases are not supported. Update to the latest and fully wipe your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itrunner:
Very good, will do. I was. Actually just going a backup for this very reason!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] itrunner:
i'm up to snuff now with the latest version. I was speaking with a friend with an unrooted nexus; he described similar scenario when he's an out of service area, and then returns to a serviced area. seems like his never switched back on-to the network. i do know where i am LTE is a bit sketchy, i wonder if i'm dropping out of LTE then it never re-connects. I'm going to try setting to just GSM / WCDMA and see if it stays connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Please read the OP and use the linked Q&A thread for this kind of thing. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
I think I found a bug and I don't see anyone reported it... Every time I'm streaming music (no matter the app) over bluetooth if I get a phone call while streaming, it will sound the ringtone over Bluetooth and change the music output to external speaker allowing all around to hear music playing. When I answer the phone call it then stood the music but as long as the call is ringing it plays music over speakerphone.

I'm pretty sure this wouldn't be default behavior nor app related since its happened with different apps and different BT devices.

I will loom at the bug reporting stuff just not sure what I would need to submit for this

.....sorry in advance lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please wait to post until you have the proper information to post when reporting bugs. There's nothing that will be looked into without it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
Will do, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RepublicanJesus:
Hookup in USB Debugging

Be listening to music over Bluetooth

adb logcat > stuff.txt

Call your phone

Ctrl-C once it has been logged
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Task a while back someone brought up adding an option to show the lockscreen slider before a secure unlock. Thought it'd be a pretty cool option and I think i found it in Slim's source. Check it out let me know if I can help.

https://github.com/SlimRoms/packages_apps_Settings/commit/700bd9f9c7f79ec33269c07d2c08a086446885fe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
Original issue:

Thanks alot for the instructions! :cowboy::good:

Here's my adb log for this issue. Funny enough while I was working on this, I encountered the "Turning bluetooth off......." error from past builds. I had to restart BT service. IDK if that issue is included in this adb log or not. If it is not I'll re-report that issue when it comes up again.

http://db.tt/3253Fg81

Hopefully I did the adb logging right...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're missing a commit. That's 2/2. You'll need to find 1/2 also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Yep, the 1/2 commit should be in frameworks_base.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. I know that. What I'm saying is that he didn't include it. He only posted half of the commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Here ya go:

https://github.com/SlimRoms/framewo...c93f/core/java/android/provider/Settings.java

Edit: Fixed link
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks. Probably not going to be adding anything any time soon due to me working two jobs now. Won't have the time for a while from what its looking like. But I wanted you to search for it anyways because you were the one wondering how to find commits the other day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
No worries, the codes there if you feel like adding it. But yea finding commits sucks. I wanted to search for the string of the option but it's not that simple for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I noticed because you didn't even link to the proper commit. You just linked to the whole frameworks_base commit log. Also. There are quite a few differences between AOKP or my sources when compared to slims. So it would take some work on my side to get everything correct and in the appropriate places. Its not as easy as just cherry-picking and pushing. This is the commit you needed to grab.

https://github.com/SlimRoms/frameworks_base/commit/55f439169e49ecb71a880e52694aca5d2000c93f
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
My bad, did it from my phone browser. Correct link is below. If it's a ton of work don't worry about it. I was thinking you could just copy and paste it in.

https://github.com/SlimRoms/framewo...c93f/core/java/android/provider/Settings.java
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Look at the post above...

Also. You can't just copy and paste something like.... src/com/android/settings/slim/LockscreenInterface.java when AOKP source doesn't use that method for the lock interface. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Thanks for taking a look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jainyankee1993:
Still getting no lock on gps.. Latest update.. Clean install... Anyone have any suggestions. Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. I have a couple suggestions.

1.) This is a development thread. Please use it as one. There is a place for questions like these and there has always been a link conveniently located in the OP of this thread.

2.) http://xdaforums.com/showthread.php?t=1781242
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
I had 2 random reboots last night. I was using gps tracking, while listening to music over BT. When I tried making a phone call my phone rebooted.

The crazy thing is while it was rebooting on the boot logo, it started dialing/ringing the person I was calling!! WTF? lol.... So, by the time it came back up to the home screen I had reached voicemail for the person I had called before the reboot, weird!

Anyway, I tried resuming services and tried calling person again and the exact same thing happened. I took a last_kmesg and dmesg using syslog after it came back up on the 1st reboot. Hopefully this has the info random reboot and call "outside of os" haha...

last_kmsg.log: http://db.tt/tkCuhknC

dmesg: http://db.tt/x9jSWWhE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What have you done to try and fix this on your own? What settings have you tried to change that might help. What have you cleared data for? I have seen none of this and I can't possibly get every device to work correctly considering the difference across all devices. It's up to you guys to find the settings that will work for you also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
Just because no one else reported doesn't mean it ain't there, no? Plus, you don't use BT correct? Perhaps it's related to BT or a combination of things. I'm not asking you to fix it just reporting it. Didn't you want reports of random reboots with logging? I'm confused...

I can help if I know how. The reboots appeared to be os/build related since it happened 2x in a row and happened when I tried to make a phone call. Also, it started ringing the person during the reboot, weird.

I see you mention tweaking settings on my end. No idea what to tweak, everything is on default settings pretty much on the rom side. I have changed no performance/kernel/os settings. I'll see what I can figure out though, thanks. Just thought you wanted to know. Hopefully a future build will fix or I will stumble on an answer. I'll see what I can do to fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) I don't care if any one else has reported it or not. That's not my point here. But for you to just flash the ROM, have issue, and then not try anything on your side isn't really of any benefit to you. With all these devices not being created equally it is then up to the user to try out different settings to find the ones that will work better for that particular device. So by leaving everything at stock values doesn't really make any sense. I don't own your device. I own my device. And my device is different than yours.

2.) Just saying that you think it's OS related doesn't really really apply here considering I could easily say it's not because I haven't seen any of the issues that you have.

3.) I use bluetooth almost everyday.

4.) I've stated sooooo many times in this thread and the Q & A thread that you guys need to play around with kernel settings to see which could possibly work better for your devices. I can't do that for you. A search would've told you this.