yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
Out of curiosity, when you switched on led charging, did rom control throw up the superuser request? Mine did not, and I am having the issue. Just doing some research.

Sent from my AT&T GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juni0rz:
Anyone having issues with phone freezing while on a phone call? I get it every once in awhile ever since the 3.4 kernel.. No biggie just curious if anyone else is experiencing it. I always fully wipe...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Task, just so you know 4/5 wifi tethering didn't work for me. Neither did bluetooth. The toggle was there but the it didn't do anything.

I tried almost every device setting for tethering and it just wouldn't work. The ROM seemed fast as hell and would have liked to keep it. Unfortunately I need that tether with my ipad. Maybe down the road.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Both work. I'm tethering right now to my nexus 10 to respond to this post. I just used Bluetooth headphones also. You are doing something wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please follow XDA rules and search before posting. You are beating a dead horse for the millionth time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 78Staff:
deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I didn't have to do anything. My settings carried over with this update. I wiped cache/dalvik cache and flashed the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Mine as well...good job Task!

---------- Post added at 07:27 AM ---------- Previous post was at 07:19 AM ----------

Been seeing it too..just part of 3.4 & the process of development. Fullwipeaholic here as well. I believe some of our devices just dont take as well to it as others.It will get fixed sooner or later. Task may not put up with BS but one thing is for sure he addresses & edifies our phones to places major phone corporations can't even come close to!:victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gsm22:
No sound on latest release/3.4 kernel

Hey guys. I seem to be getting no sound from the phone with the latest releases which feature the 3.4 kernel. Tried full wipes/formatting system and still no luck. Checked the settings for touch sounds etc.

I searched the thread and it looks like no one else is having the issue, so it's unlikely to be addressed I guess. It's probably my phone not liking the latest kernel; I've tried flashing the latest cm10/paranoid android as well and no matter what I try...zero sound from the phone :(

The newest 4/5 release seems awesome from what little time I spent with it, but I use my phone for music a lot, so not having sound is a deal breaker. Ringtones don't seem to work either.

The latest release that works for me is 3/13. I've tried all the latest releases with and without the ktoonsez kernel, still nothing.

Any words of advice or tips would be greatly appreciated. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] multiduplikator:
Maybe you can install faux sound app and check the gain settings...sound like all is muted...just a guess
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
is it a good idea to just flash the latest rendition of task's kernel but not update the ROM? I'm feeling lazy to fully wipe and set up but I want to fix the kernel issues. would that cause more problems or would that be okay? -curious-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] multiduplikator:
audio stutter and clicks on 4.5

Hi guys,

Audio stutter and clicks are back for sure in the 4.5 release.

They are best and loudly noticed when playing with headset at lowest audible volume.

Tried to do something about it with faux sound app...no good.

Flashed ktoonsez kernel...and all is fine!

A lot less background noise, no stutter, no clicks, perfect overlay of sounds.

What is the difference wrt audio between the two kernels? Faux?

Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Update to the latest release. It had all new update drivers that you might want to try.

P.S- I wouldn't recommend flashing anything when you are feeling lazy. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Im not having any audio stutter. Not sure what to tell you.

If you're using ktoonsez's kernel I'm not sure I see the problem here? You're not even using my kernel.

We both have faux sound integrated into in our kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task by any chance are you experiencing low call volume on your device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Okay thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not at all. Sound settings are set at stock values. They used to be waaaaay too high and way above stock values to the point to where they could almost blow the speakers when in call and/or on speakerphone. But they are right where they need to be now. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
OK got ya thanks for the info Task! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] multiduplikator:
I am using your kernel normally. I flashed ktoonsez a few minutes ago to see if the problem persists.

Contrary to the firmer post (which I will correct shortly) the stuttering when overlaying sounds is also present in ktoonsez, but not the clicks.

To reproduce this:

Set volume level to one step above 0.

Use Audiobook 303, set sleep timer to something short, and start playback of a file.

Use seek buttons - clicks will appear.

Wait for sleep timer notification - stutter will appear.

I tried this on the past versions of your ROM (see earlier post) and it was working before using the same app.

The issue is present in other players as well - at least for me.

what can I do to help fixing this...do a recording of what I observe?

Let me know
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't have audiobook or anything like that so I can't test that. A recording won't do anything in terms of troubleshooting. But if you know your way around source you can always take a look through mine, CMs, or AOKPs source to see if you can find the culprit. If not. You will just have to wait it out for now or flash back to a prior release until this is resolved. With the new kernel implementation, new drivers, and latest changes these things are bound to happen and it's only a matter of time until things like this are fixed. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Preface: I followed instructions when installing. Install went very smoothly.

Tethering: I'm using TrevE Mod. Is that the one you're using? If so what device setting are you using?

Bluetooth: Bluetooth toggle from the pull down didn't respond. I long pressed it and got me into the settings view with the On/Off slider. The slider didn't work. It would sort of light up but it would not slide over and stay over. Rebooted phone and still didn't work.

What do you think about the bluetooth? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) I'm not using any "mod" to use tethering. This ROM has built in tethering and no "mod" is necessary.

2.) This Bluetooth issue you're having is strictly user error. I'm not sure what to tell you on that one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Alright I'm gonna give it another shot. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Good luck. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
Is there a way to uninstall the default superuser app? I'm having issues with better battery stats, and the suggestion is to try a different superuser app. Problem is, I can't figure out how to disable the default one. It isn't under manage apps, Titanium backup doesn't show it, and there is no superuser apk in the system/apps folder. I'm not sure where else to look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Look in settings under superuser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
Ok. Under settings > superuser I have a list of approved apps, and nothing else.

Under settings > superuser > settings, I disabled superuser access, and anything requesting access was denied, even though I had installed a different SU app and rebooted. I must be missing something, sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you want to use another superuser then just do that. You dont need to get rid of the other one in order to use a different one. It seems as though your problem isn't superuser. It's the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
You would think it was the app, but better battery stats is insisting that if superuser permission isn't sticking it is the superuser app, not BBS. And permission definitely isn't sticking, so I figured I would try what they said.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
Could someone please post their quantum benchmark stats? I'm getting worse stats than stock!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please don't start this here. Benchmarks on android devices are nothing but random numbers generators that mean absolutely nothing in terms of how the device works. This thread is to support questions that pertain to this ROM and to support those useful questions. Benchmarks have nothing to do with this ROM.

Ask yourself a couple questions:

1.) Does the device really feel as slow as the benchmarks?

2.) Does the device on this ROM really feel that much slower than stock ROMs?

I bet you will probably answer no to both of those questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
Alright thanks. I guess benchmarks are not reliable then. My apologies for for starting something unwanted in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] multiduplikator:
Thanks for the feedback.

I will continue to use the latest build as I can live with it for now.

If I come across a future build that fixes it, I am going to post an update.

Cheers and thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Happened once today but probably a fluke. Up until today my son had no voice mailbox set up for some reason and when I called him today it rang for awhile then forwarded to an ATT recording. My phone froze up and I had to remove the battery. Hasn't froze since and after I had him set up his VM it's fine.

I'm blaming Apple since he's a fanboy with an iPhone 5;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Does anyone know a fix for the msm_otg wakelock besides rebooting? I've searched for solutions and causes of this but to no avail. From what I've read it's a kernel thing... Any suggestions would be appreciated

Thanks

Edit: sorry forgot to say what I'm running.

Fresh install of 4/5 wiped all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Don't boot your device with the usb plugged in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason_Nguyen:
I'm on 4/5 is charging led toggle not working for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Just tried it - can't get it to stick. Full wiped this afternoon, but I don't normally use it so I can't offer anything past that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
working here;) I went & double checked & all seems to be working right here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
Mine is not either. I'm trying to look into this, and I am still stuck on rom control not asking for superuser permissions. I'm kind of feeling they might be related. Any insight on this?

Sent from my AT&T GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You're stuck on that, and I don't think it's relevant or Task would have said so yesterday. I think it's just a tweak/glitch and patience is the way to go ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aklbeach:
Having issues getting my sd card to mount. It's a 64 gig card and has worked fine for the past two months. I'm running the 3/10 build with the kernel that comes with it. Haven't had time to upgrade. When I go to storage and try and mount I get nothing. When I physically pull the card out and reinstall the symbol comes up for a while, then nothing. Went in to recovery and mounted external sd and it let's me see the card and files in recovery. I'm out of town and haven't been able to put the card in a pc and try and also can't search in taptalk. So apologize if this has been posted. Any ideas?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You're almost a month behind, and only the current build is supported. I would download, nandroid and full wipe and install the current build. Even if there are problems, at least then we could help.

Also, if full wipe doesn't do it, it's probably the card going "bleh" and you should probably copy everything off, format and copy back. It does happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aklbeach:
Yea work as kept me busy and haven't updated lately. Other issue is I won't have a recent titanium Backup for apps if it won't write to the card either guess I can change that to the permanent storage. That won't get lost when you Rom, correct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ericjackson:
I'm still getting lockups when ending a call that makes me have to hold the pwr to reboot is that a bug? I have wiped everything and reinstalled

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
That's a please search first, and reported more times than you would believe. Answer is to revert to an earlier build if you can't wait for Task to tweak it up. It's still a WIP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're beating a dead horse here for the millionth time. Please at least search before posting to avoid unnecessary clutter in this thread. This is something that has been asked and answered quite a few times already. There should be no need to go over it again. :D

*Hint*

Try raising the minimize clock speed. Or do as the above post states. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
2nd round and I gotta say nice f&cking ROM so far. Definitely a lot faster than stock JB. Everything's working so far so good for now. Hopefully battery life is as good as stock. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Emil9727:
Ok so I have 2 questions.

1. Did you apply any patches or make any modifications to Gps related stuff? This rom has the best gps for me.

2. When I plug my phone into the charger it gets... Studdery. Like this hang here and there and all around its not smooth. Anyone else getting that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
For the wake lock bug, is it only caused by the device being booted via USB to computer? Or any power supply whatsoever?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
This is the commit that kt merged to fix it on his kernel, not sure if it would be the same though.

https://github.com/ktoonsez/KT747-JB/commit/f735dd79b031409263bf531f557af85a39e93321
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Any power supply. I never boot while plugged into PC, but I've read that it happens plugged into PC as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 78Staff:
You don't need to disable it, just install Su of your choice (I use SuperSu, for instance), it will install it's own binary and you are good to go.

---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------

I ran into a similar issue with SuperUser and Tasker's root access running shell scripts, search back I posted in more detail on it. The work around is to create a dummy superuser.apk file in /system/app, set perms to 644 and restart. Tasker (and, possibly BBS I suppose) will see the file in place and work correctly. You can try this, and if that doesn't work then you can then switch over to another su like SuperSU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CyclingVinnie:
Task, what launcher are you using? You comments about Nova in the development thread got me thinking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fvargasfrank:
Hello, my phone freezes every 1 minute using new release, when I try to downgrade to 3.6.13 it won't let me it gives me and error. Any help please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Adelaide.:
I tired installing a second SU app over the default one and BBS still wouldn't work, which is when I started looking for how to disable the nature superuser. I ended up getting superSU to work after some trial and error. I had to disable the native superuser, restart, install superSU and then restart again for it to stick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Just out of curiosity what kernel are you guys running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
ktoonsez JB 7-28

ill get a logcat next time it boots up after flashing... usb debug should be default, so hopefully it'll grab it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rayoubi:
When I talk on the phone I can hear my voice echoing. any fix for it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Without a log cat or some sort of information. Nope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rodger-sp:
To Task & ktoonsez will you be doing any new updates on the ICS ROM or is all of your time going into the JB ROM.

I am very thankful to you both for all your hard work.

from my AOKP galaxy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Were probably going to support both. But Jellybean is the main focus right now considering all the work that has to be done. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
my macbook is no longer reading my phone when i plug it in, what could it be? i tried mtp and ptp with android file transfer but nothing =/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pudge12:
I wiped and reflashed including the included gaaps, but I'm still having the sane issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
It's an issue with AOSP ROMs right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
dam =( this is bad lol, im sure theres a work around, i need to figure it out, this is one of the reasons i hate my mbp.. =(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
lol i still love it! best laptop in the world!! she just dont get along well with little green androids..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rodger-sp:
OK thanks for the info.

Keep up the great work!!

from my AOKP galaxy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Haunt3r:
I can second this issue. Hopefully it disappears soon. Other than this running flawlessly on the 2/27 build. Waiting for another build to flash again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
i have that issue but i found that restarting my phone gets rid of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Haunt3r:
I can also second this. I don't know what causes it in the first place, I turned on my touch sound as well to hopefully prevent it from happening. Not that I like it, but a fix is a fix. :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] quattrob8:
Will MHL ->HDMI ever be supported?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
sure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
yeah, it's a fix. if you don't want to do that you can roll back to the first jb aokp build and it appears to work normally. that's what I did to get around this bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lostsoul565:
rom and kernel question

so i flashed this rom 7/28 and Ktoonsez kt747 kernel. i just want to make sure this is the correct kernel because this is aokp and on the kernel page it said to make sure you have aosp rom??? a little confused. everything is working fine but i don't see any way to edit the kernel settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Anyone having scroll issue? My screen is moving up and down by itself when browsing the Web, looking at messages etc lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You are the only one to report this. One question. What kernel are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
I did what Task suggested and raised my clock speed. Solved the random freezing and reboot issues I was having
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Your kernel. Then I tried ktoonz same thing. I should have quoted my reply. This is in response to task. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The only reports I've seen are from users over in ktoonsez's kernel thread. So it looks like that is your problem. Fully wipe and reflash the ROM without flashing ktoonsez's kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
That's what I'm thinking of doing. Thanks much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Giskarded:
I've had the same issue as humble.

Stock browser will randomly scroll up and down.

I've done full wipe last few times to no avail.

Tasks kernel. This issue has been on the release from 3/31 onwards.

Another issue has been with the play store closing automatically on initial opening sometimes it closes a couple of times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I also have the scrolling issue. I'm not the only one either, a few others said something about it in ktoonsez's thread. I tried both your kernel and ktoonsez, both using different governor/scheduler combos with no luck. A clean install also doesn't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
With only 2 people out of over 9,000 downloads and both of you having tried ktoonsez's kernel, it seems to me there must be something you guys have in common. Not much I can do considering I've seen nothing of the sort and neither have 9,782 users that have downloaded and flashed. Not really sure what to tell you two. The only reports I've seen are in ktoonsez's thread so it looks as though there is a common denominator here. I guess ktoonsez released a kernel that fixes the issue. And from what I see, the things he changed have nothing in common with my kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Yeah, I was just waiting for a future release to see what might happen, but I notice the scrolling issue. Happens in multiple browsers, Wikipedia app, tapatalk etc.

The screen just jumps up then down quickly. Things like that.

It's not a non stop stuttering... just a quick jerk that happens every few minutes, usually shortly after scrolling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Fully wipe your device. Or try upping the min clock speed. Now that there's three of you that have yet to post any information to troubleshoot a non existent bug on my device, you guys should team up and figure out why you are having the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You guys should always at least trying to up the minimum clock speed to see if some of the issues will go away. With this being a new kernel it's not going to run exactly like the 3.0.x kernels in prior releases. Seem like a lot of issues have gone away for others by doing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
What kind of information do we need to submit? This is a weird scenario. Will catlog do? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Whats a catlog? ;)

First fully wipe your device. Then up the min clock speed. Then go from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
I've set my min to 594 and it's the same thing. Ill try higher.