yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arktik:
Anyone else having this problem?

When I put the phone on vibrate and then eventually go into spotify and try to play music, i go to turn up volume and it wont. I then remember its on vibrate, go into the settings drop down, turn it on regular (and hear the beep acknowledging it) but the media volume stays locked. I can adjust notification and alarm but not media. I have to reboot the phone to get media volume to unlock to be turned up.

Is this user error or a bug?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gavingreystone@gmail.com:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

In settings>sounds>volumes do you have volumes linked?

Also possibly safe headset volume in settings>sounds, try unchecking it. It can make certain apps force close when trying to turn up the volume. If these don't help then Google is your friend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
I would, but then I can't distinguish what is what. I love the LEDs cause instead of using different notification sounds for each app, I can just use a different color :laugh:

But this is no big deal in the long run of things. This is the first time I've ever seen in it all of the builds Task has made. I sure as hell won't switch to another rom just for this. Now if he sets my phone on fire, maybe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] exploitz:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

Using lightflow doesn't cause this issue to occur. I've been using it for awhile now because it offers a little more control over my led than the built in led control
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Tried it, hated it. Anyway, enough of this topic. Causing clutter now that it's resolved and the cause explained.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rockynewsmaster:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

Is there a way to install Samsung's video app on this ROM? I really wanna beam some videos to a friend who has stock ROM and won't let us without Samsung video app

Or if anybody knows a work around for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

Wrong thread for this buddy... only things supported here are what is available in the OP. No TW stuff or 3rd party apps...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
task650 you know I wouldnt do this normaly, but as of latest update I am having wifi issues myself.....no i dont have logcat, I will get that next time, but I can explain what happens exactly. after being connected to home wifi, then turning off before leaving home, then after I get home from work, re enable wifi, go to setting and watch wifi status go from connect, obtain wifi address, then disconnect, rinse repeat... will not reconnect untill reboot, home connection is wpa2, I will be re testing with logcat to try and determine the exact culprit... using latest rom of course, with ktoonz kernel(latest), underclocked to 1409mhz, no voltage adjustments. I will reflash with pure stock if need be. but hoping I can help if it isnt kernel related :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you flash ktoonsez's kernel then you need to go to that thread for support as i only support what i package in the OP of this thread. How am I (or you) supposed to be able to tell if it's rom or kernel related if you don't just use what I provide? You're just making it difficult by not using what's in the OP. I have no wifi issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rattles:
have you tried it with the kernel that comes with this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
LED colors have been brought up numerous times, and they have their own thread, please search for this, it has been brought up more times than anything

---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------

I just flashed this 48 hours ago, noticed the issue today, hard to do all this in such short time, just noting the issue, as previous people had stock kernels
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You should probably try reading all the posts that go along with that one before posting. Then you would probably know that they don't need to search for this. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
reading all the threads for this rom is insane lol, if I was out of place my bad....I spend 20 minutes every 12 hours on this thread lol.....sorry

---------- Post added at 07:59 PM ---------- Previous post was at 07:50 PM ----------

yes, I'm about to reflash with stock rom, I also apologise is I found said LED post.. I skipped that page(of course), I will retest within the hour just to let the phone go though its paces, if it turns out to be kernel, i will adjust to said topic and inform there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] b0u1d3r:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

I am having the same issue with the included kernel. I did not have the wifi issue on the previous build.

I am also having an issue with my cell connection too. Both connections drop for no apparent reason and randomly. I have to reboot the phone to get service back or wifi back.

And yes I always follow the steps of proper flashing. I re flashed as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InfiniteImp:
I had that happen as well. Somewhere between my 2.10.2013 flash and the release before that. Wanted to copy an APK onto the phone and realized it wasn't visible! A reboot brought the phone back, but only for maybe 10 seconds, then it disappeared again. Same cable I've always used, no change in fast charge settings. It did this for the rest of the evening. I rebooted a few more times and it went away. Now every time I plug it in, it shows fine on the computer. Like nothing had ever gone wrong. Weirdest thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Royalmathmtcs:
I'm having the issue with WiFi cutting out and not reconnecting without a reboot. Latest build (2.10.2013), full wipe, and using the kernel that comes with the ROM. Otherwise, this is the best build to date for me. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sounds perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niabi:
well just to get a smart ass reply as well :p ... I am also having WiFi problems, not only cutting off, but I am about 1 meter away from my router and it gets 1 bar signal (on AT&T stock I got full bars all over my house) if I reboot the phone then the WiFi works correctly for a few minutes/hours (its random), I did a clean wipe, I installed the newest kernel, and come directly from stock (this is my first ROM on SG3).

just reporting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That sounds good. Glad to hear. ;)

P.S- Fix it then dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

Here is one for you. I have not had a single issue with wifi at all. As a matter of fact my signal is stronger now then it was on stock. Sitting outside my house in the back 2 floors down from my router and still full bars. When you say you full wiped you did do more then a cache cleaning and factory reset right?

Wayne Tech S-III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@Everyone

Talking about bugs will not get you any closer to fixing the issue you may or may not be having. WiFi is just fine for me. So either you guys fix it on your own or provide the proper information. Its a waste of space without it. This especially applies to things that I do not see. How do you expect me to fix something that is not there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Same here. No issues whatsoever. Actually better than ever lately. Looks as though people would rather talk about these issues rather than fix them. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Mine is fine too - apparently you're supposed to be magic if just enough people report it without helping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Pretty much. I'm not changing anything. Its fine how it is. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Hey Task, I've been having a weird issue and I tried a few searches, but not sure what to search for :P

When I'm on a call, it sounds like me or the other person is hitting buttons (once in a few minutes or so, it's random during the call). I thought it was just my mom, but I've been hearing it with everyone. I've tried seeing if my cheek is pushing something or whatever and I can't find any "hidden buttons" while on a call. And all these people also say they didn't hit any buttons, nor do they even hear it. Are you hearing this too? I've had it for a while, and I've fully wiped a few times since then. Thanks Task! Great rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm on the phone for almost half of my day everyday and have not heard anything like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You should learn to read before posting this nonsense. There's such a thing as an OP (The first page of this thread) which contains the FAQ, which will tell you the proper way to submit a bug report. If you guys don't want to help me to help you then you're on your own. Do you really think I can fix something that isn't happening? If it is happening to you guys then prove it. I'm not here to play the guessing game dude. Part of this thread depends on you guys to provide logcats, last_kmsg, ect.. Educate yourself with the basics before posting in a development thread and please stop acting out like a child. Stupid? Well i would think twice about calling someone or something that considering what you have just stated. All it takes is a couple minutes of reading. I can't hold your hand through that. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousDiarrhea:
Had it happen to me once as well, but in the last build. Haven't had it since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niabi:
I am not defending the other guy (insults get you nowhere) but just felt like replying to this... the FAQ says and I quote

"Also it would be beneficial if some logcats were included with bug/problem reporting."

what it doesn't say is:

"IF YOU DON'T PROVIDE LOGCATS DON'T REPORT PROBLEMS"

anyways, just wanted to post that out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's a proper way to report bugs and everything is explained in detail in the OP of this thread. I don't expect anyone to be knowledgeable at all. All i expect is that the OP is read and that should take care of the rest. What you think makes no difference and doesn't belong here. If you can't follow something as simple as a couple minutes of reading, then you shouldn't be posting here nor should you be flashing custom roms. Your logic makes no sense with the "No reporting....". Read the OP and then you would know exactly how to report. How do you expect me to fix something that doesn't exist for me? Well. The logical thing to do would be to provide a logcat in order for me to even see it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

The BS stops NOW, or infractions will be handed out!!!

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
7. Bugs/reporting

1. bug reports here should contain a logcat or information

that would help. saying this doesn't work or this is happening doesn't help us

at all and at that point belongs in Q&A. task 650

2. Some bugs are being reported by a few that Task, Ktoon and others are not

seeing. Follow avidmovies notes below on trouble shooting/comprehensive reflash

and Task's suggestion above on weird sh!t. Stick to the basics and see if

problem is there still - such as stay with kernel that is included with rom,

skip restoring anything with titanium back up, other words just try the basics

and if a certain app has been giving you problems download it from the market

instead of tibu and see if problem still persists. Some apps have been

reported to make ROM features malfunction.

3. If you had a spontanious reboot, we need the file last_kmsg from the

/proc folder.

4. If you have n FC on an app, thats when we want a logcat task650

5. Guide on how to logcat. http://xdaforums.com/showthread.php?t=1726238

6. All In One Android Logger > AIOlog

7. Catlog - https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5ub2xhbmxhd3Nvbi5sb2djYXQiXQ..

8. If you do not have the latest update of this rom consider it unsupported.

This is why they update- to get rid of the bugs that we may be having on older

versions.

9. BUG REPORTING: Very minimal at least read the thread from the date of the

update you are running. If you see a couple posts about a paticular bug then

consider it noted by Task. He does read these. Remember if he can't duplicate

the problem then they sure as hell can't fix it. Bug reports without a logcat or a random reboots without a last_kmsg will be ignored by Task.

10. thanks for understanding that after a few bug reports are made and i

acknowledge them, that the unecessary 100 that follow are ridiculous. Task

Fixed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

People, please....... READ THE OP carefully........ so many misread the text thinking they understood but really do not......

Also, if there is a posting issue please report it...... do not ramble on on posting protocol or etiquette ..... this ends up derailing the topic.........

Stay on topic......... but always post respectfully or do not post.....

......Thanks ~~~ oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

I just had it happen to me while talking to a Direct TV person. I thought it was on her end until I read some of the other posts. Just figured I'd mention. First time it has happened and hasn't happened any other time since the update. I wipe everything every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

I've always made it a habit to reboot my router before connecting a freshly flashed phone to it... Maybe its placebo but the test doesn't lie... So I would suggest including that as a troubleshooting step when wireless is mentioned...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

You have some badass internet there Sir. :) but you are correct. They might want to check their router and make sure others aren't stealing their bandwidth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I am reading all these posts about Wifi issues and I am like huh? My Wifi is working as it should sounds like they need a FULL wipe to me :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. I'd say wifi has been pretty good for me too. Not as fast as what I get on my computer, but still pretty good. Comcast has been f'd up these last two weeks also.

Phone

Computer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

After dirty flashing about the last twelve releases I started seeing a couple of weird issues that looked like Rom problems, rare screen jitters, camera turn crash etc. Then I followed the op and reloaded the phone and all my issues magically went away. Heed tasks' advice folks. It's like a cool new phone again.

It's mostly no work to do either. Before you start, and probably on a regular basis...Use your launcher backup to save app/screen layouts, use ti backup to backup all apps and data.

Take a nandroid.

All your apps should magically dl from the play store. After they do run your launcher restore.

Finally and after you reload, restore data-only in ti to get back your setting and login info for individual apps

Enjoy a minty fresh phone experience.

Thanks task, you kick bootay.

One nation under a groove, gettin down just for the funk of it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dalewest:
Beeps during calls

For those reporting occasional beeps during calls...

I get them on occasion too, but I'm sure that it's not ROM related. I think it's a handoff issue when moving from one cell tower to the next, since when it happens for me, I'm always cruising down the road in my car.

If it bugs you, maybe try a different modem/radio?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
He posted this in the PAC-Man thread.

But to answer your question, no ETA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liquidfiend:
I had random screen jitters after changing and testing the LED colors, but all I did was reboot it and it was fine. Is that possibly what was happening to you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't plan anything that I do on XDA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
I haven't observed any reboots since the new kernel.

Thanks for the update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Had the same thing. First obviously do a clean wipe. Then when you are unable to connect restart phone. Wifi shoud reconnect on boot, for me this connection lasted ~2 hours then it would get stuck on "Obtaining IP". Then I would restart again and it would basically do the same thing again. I did this maybe 2 more times and now Wifi works better than ever. Haven't had an issue in 1.5 days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
.....................
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

I've run into WiFi not connecting usually after a new flash. Just deleting the WiFi connection and re adding it usually fixed it if toggling WiFi didn't work. But I also have 3 routers in my house with the same ssid
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Camera

I searched everything I could think of but couldn't find a post. I'm pretty sure when you first open the "camcorder" part of the camera app it pops up a message that says "touch screen to take photo during recording" or something like that. It's not a big deal...but I don't see it working. Is it supposed to work? Did I imagine the message? Or is the message there and it's not working yet?

Thanks for any input!

PS. I know you don't need this TASK, but just felt like sayin'. The camera is the only part of the ROM that could use any improvement from my perspective (my perspective....I'm a user that gets to use your ROM at no charge and enjoys it...at no charge....man I wish I had the know-how and time to develop). I flashed over to a couple of TW ROM's just to get the camera back....but I couldn't stay. Your ROM has pretty much everything else I could want...looks good, runs fast and does pretty much everything else....better. I say this to say THANK YOU for sharing!

And, Happy Valentine's Day ya big lug! (no homo) :D:good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
That isn't implemented on this ROM yet. It has been discussed somewhere in here...;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
You aren't going to get a TW camera on an AOSP ROM. Different frameworks. There are third party apps you can use. Or you can figure out how to port TW framework into AOSP and make your own badass ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All it takes is a second to click a link and read. My source is always open and available for everyone to see what I'm doing or whats going on. It's even built into the About AOKP section of ROM Control.

https://github.com/task650/android_...mmit/ec348e5d72e9b3122ffc68be6bf35ee65df0735f
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Dang...if that's the case...I REALLY wish I could figure out the magic of searching for the right terms on here. Maybe we need a "word bank" in the OP. "If you're having problems with XXXXXX......use these words to communicate it in your post.....XXXX XXXX XXXX" Too many people have too many ways of thinking about and saying the same things. :laugh:

Thanks for "making that clear" Al. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Sometimes the right search doesn't work as planned in XDA. I always search in Google and often get a link right back to the appropriate XDA post. Or I get a link to a non-XDA source that still has the correct information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
So....in my "unknowing" ways, just want to make sure what "clicking on a link and reading" addresses.

Are you saying:

1. "not working yet....it's coming...here's the commit I submitted" ("you're a mind reader dude!" I know...too far...;))

2. "if you want to figure out how to code....look at this stuff and and go here...you'll get there"

3. "look here before you ask questions" (if that's the case, I probably don't stand a chance...I couldn't even get ADB working properly...much less understand what exactly some lines of code address....although that one is pretty obvious)

4. NOTA.....get off my thread!

Just trying to understand your language and thought processes....I didn't major in Psychology....but I like to communicate clearly and stay out of the way as much as possible! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kafepuya:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

You may have a point there. However, I would suggest to not just read the OP, FAQ and Q&A before flash or when you come across a problem, but periodically. For example, I read the FAQ every 2 weeks, because this ROM gets updated quiete often. And I don't do it just for this ROM. I also closely follow 3 others threads in Original Android Development and their respective support threads. Usually, when someone reports a "problem" here, I already know what the issue is, and just by reading their post I can tell if that person has read the OP and FAQ or not.

If you take into account how often this ROM is updated, how popular it is, how many people post here, it's really a no-brainer to keep up with the changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Changes are made there. Look there in the respective repo (yours was a camera question, so look in packages_apps_Camera) that you have the question about first and you might see what you are going to ask the question about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm not going to put a "How to search" in my OP though. Too much work for me (I already do enough I think) and just changing different variations of the search terms will usually bring up good results. Google with "XDA" at the end of it is pretty solid also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kafepuya:
Re: [ROM] AOKP(Jellybean 4.2.1 )Task650 (2.10.2013) (AT&T)

No man, all I trying to get across to him is that even if there was a word bank, as he calls it, he would be better served if he just followed more closely the thread and the FAQ. I'm not suggesting that you modify the thread in any way. :beer: