yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, has anyone else have this problem? I can't install apps, the install button doesn't work. I did a clean install and at first it worked, after a reboot it stopped working. Also, when I double tap the screen, it zooms in double tap again to zoom out. I would greatly appreciate any help. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I can't help on the install problem. I presume you are talking about clicking the Install from Google Play. Do you get an error, or just nothing happens? is the button greyed out?

On the double tap, I'm thinking maybe you must have Magnification Gestures turned on. Go to Settings, Accessibility, and be sure Magnification Gestures is turned off. See if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gsm22:
do you have any kind of screen filter/dimmer installed? the screen overlay makes it so that the install button doesn't respond

might be some kind of magnification option you have enabled in Accessibility settings for the 2nd problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Tried to install and or update app in Amazon Market, no go. Tried to install an app in root explorer or es explorer also no go. I uninstalled Lux and was able to install. Magnification gestures was on, turned off. Thanks for the suggestions and the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgoe:
I have tried multiple times to install gapps 6.19 but I get abort every time. Thought it might just be bad download but ruled that out. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The same suggestion that's been posted 8 million times... use a different gapps package. There's only about 100 out there on the internet. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgoe:
Will do. No biggie I am using 5.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
I have a small request, if an option to separate the ringer and alert volumes like the older roms have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leeroyjenks:
Can I flash a different kernel on the 6-28 update? I posted earlier about the signal dropping constantly and someone in another thread suggested a different kernel doing better with att on the s3.

As always, thanks task!

Sent from awesomeness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
I've been all over this ROM looking for a way to set the lock ring slider shortcuts. Is there a way to set these and maybe I'm not finding it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Gmail / 3rd Party Gmail Connectivity Issues

Device: Verizon Galaxy S3

ROM: Task650 AOKP 6/17 (6/28 was causing persistent wakelocks)

Gapps: Task650's 6/19 build

I think something if funky with my install. Are certain hosts / connections being blocked?

For as long as I've used 4.4.x ROMs, my Gmail will not show embedded images in emails, so almost all emails show the images are broken or missing.

Today I tried loading two 3rd party email apps - Mailbox (by Dropbox) and CloudMagic. Both of which use the web to setup your email account, instead of using an account on-device. When I try sign-up with either app, I get an error saying their website can not be reached or there was a connectivity error. I tried on both WiFi and cellular (Verizon) with the same result. Aside from a Chrome occasionally saying there was a network error, I have not had any other apps display similar messages.

Gmail and these apps work fine on other devices running on the same wifi network, so I'm confident it's not network related. I also do not have any Ad Blockers or security software installed.

Any idea what's going on? I'm about to try to odin back to stock and format both internal and external SD cards to see if that helps the issue.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Is there any way to pause/play music from the lock screen? The music player is beautiful when it comes up, but it becomes cumbersome to have to activate it from an unlocked device. A feature I have seen in many ROM's is holding down "Home" while the phone is locked in order to play or pause music. I can't seem to find anything like that, and I was wondering if such a thing existed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Ktweeker is a 3rd party app. You should go to the developers (ktoonsez) thread for support as that's where the info on it would be. Superuser works just fine and how it should. I have no thoughts on this considering I don't even own this device.

Abandoned? Not sure where you're getting this info. Its not solely my responsibility to answer questions. Its a community thread dude. Others are more than welcome to answer your questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Rudeness aside, the Ktweaker issues you're having aren't only on Task's ROM, they happen on other ROMs as well. The issues can come from a lot of things but chances are that Ktoon will have to figure it out with some logs.

And like Task mentioned, Superuser works like it should. If it can't give an app root permissions, you gotta consider that there might be (or might not be) an issue with the 3rd party app (no offense to Ktoon, his work is amazing!).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Ktweaker is working great for me, and the 06/28 build is going strong! My only question is the lockscreen music thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montydog:
Hi. I read through many of the posts and even searched it, but can't find the answers I need.

I'm trying to uses the Amazon app and Kindle app but always getting device registration errors. Didn't have this problem on CM 11 that I recall.

So far this is only stumbling block I've encountered with this Rom.

Anyone else had this problem? I'm on tells if that makes a difference.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) I haven't included a custom kernel in this ROM for months dude.

2.) Google works awesome for information. http://bit.ly/W3g5HX
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Use Flashify.

EDIT: Ninja Task strikes again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
That feel when no one acknowledges you :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Google search is awesome :) If none of the Google options work you're outta luck as it's not an option in this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Haven't updated the kernel? No I haven't being that I don't maintain the kernel. CM does. They do all do all the updating. I've answered this a ton of times.

I know why these forums exist. But from observing your posts for quite some time now it seems as though you've totally decided to bybass learning the basics. The basics being things that anyone and everyone should acquire prior to even thinking about flashing an android device. Its kind of why you always seem to be having issues that nobody else is having.

I already answered you dude. Use a nandroid. If you don't know how to restore just the boot.img via recovery then you should either search or go ask how to do so in the recoveries thread that you're using. These are important things you should definitely know about the recovery you are using. You download the kernel every time you download this ROM. I've also answered that (told you what its called) in this very post. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
https://github.com/AOKP Here is AOKPs source. Anything about it will be there.

Issues with launchers are not issues with this ROM. You need to take it up with the developers of those apps. But logcats would be good to post if something is force closing.

Most everything minus USB debugging isn't supposed to be saved upon reboot. Its how its always been and has been answered a million times all across the internet.

Most all ROMs (at least AOSP) require a specific bootloader (or up to a certain release) depending on the firmware. This isn't specific to just this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I only use the browser packaged with this ROM. I've never seen it on my personal devices (m8 & n5) so its not like I can personally test for this device. Not sure how it would be device specific considering it's the same browser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montydog:
Amazon Apps on AOKP

Well, I seem to have found my own answer, so posting for anyone else's benefit.

I just updated to Task's latest and thought I'd try using Titanium Backup to restore all the system settings (launcher config, shortcuts, settings, etc). First time I've tried this. TiB asked me if I wanted to restore my Device ID as the Device ID can sometimes change when doing a factory reset, so said "OK". Now my Amazon apps all seem to work fine. So either it was something in the previous ROM that broke it (unlikely, I think) or the Amazon apps need a Device ID to work properly (and are too stupid to handle a change in Device ID gracefully, like tell me that this is problem when I'm trying to log in...).

Anyway, hope this helps another Noob like me.

Other than very minor stumbling blocks like this (user errors, really), this is BEST ROM I've tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zetsui:
3. Is there a way to swipe the brightness on the top keeping it persistantly in the navigation bar (instead of having to press it first in the status bar and then slide it, or as the notification menu drops awkwardly down)? I could do this on 4.1.2 version, and part of coming back to kitkat was that it had the classic toggles/scrollable toggles. Would be nice if they had the same with the brightness which I adjust quite often.

4. In Task650's rom, are these features easily available (control animation at bootup ( iave task, ktoonsez) both coming up and loading each reboot. Control led color, led blink on bootup, the ability to dim brightness lower than the default aokp low seting)? I had them on the 4.1.2 but can't seem to find them easily? Going through all the settings, I think these are in development. Any eta based on previous releases on how long these will take?

5. Feature request in roms. Is it possible to include an airplane mode that allows you to choose what radios aren't shut on AP mode (ie hitting AP mode doesn't shut my wifi connection). My 4.1.2 setup allowed this and for me to take calls over wifi. Basically constant 100% phone network coverage in my house.

---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------

I got this too. Search my username. I had to reflash the gapps, and thankfully did not invert or would have to custom load those again. Native browser still not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
I was curious if anyone found a solution for this besides changing launchers or turning off security. I'm using the stock Google Experience Launcher and have a pattern lock enabled.

When the screen turns off (doesn't matter if lock is enabled or not) and I press the home button on the phone, it wakes the device, exits the app that's in the foreground and takes me to the homescreen. Is there a way to have it ONLY wake the device on the first press?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
I agree. It is very annoying
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Just found an Xposed module called Xposed Additions that did the trick. It's not a native fix for the ROM, but definitely solves the issue.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
I'm on Verizon and having similar issues with ALL 4.4.3 and 4.4.4 ROMs. The SSL Protocol Error was causing Gmail images to not load as well. I also have a feeling it was making my GPS wonky because I used the High Accuracy setting, which relies on Google for placement, before going to the GPS.

Since I never found a solution, I decided to revert back to the 6/3 4.4.2 release of Task650's AOKP. It solves all the SSL issues that I was receiving on newer versions.

---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------

I'm thrilled running the 4.4.2 6/3 release because it solves all the issues I was having with newer versions, except battery life. It doesn't seem as good as I expect, especially screen-on time.

Kernels - so far I've tried LeanKernel, KT747 and BMS. All give about the same battery life and performance.

I also odexed the ROM, since that is suppose to help with RAM and battery. I can still change themes too.

Any tips to get better screen-on time, besides lowering the brightness? Any performance suites like PurePerformance or Operation Killjoy? Performance on the ROM is fine, I'm just looking to pick up battery.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Can anyone on the 7/14 build tell me what the SELinux status is reporting (Settings > About Phone > SELinux status)?

I'm still trying to figure out why all 4.4.3 and 4.4.4 ROMs are giving me SSL Protocol issues when connecting to some Google services. I'm currently on Task's 6/3 4.4.2 build and it works brilliantly for me. SELinux status is reporting "Enforcing".

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Same reporting on latest build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Hey all,

Anyone use the Tumblr app? I'm on the latest build and upon running the app, my phone freezes and I have to pull the battery. Anyone else experiencing this? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, updated to 7/29 and could not get wifi to open. Redid it 3 times but still no wifi. Went back to 7/21. All is well except for the occasional reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Wifi worked fine when I flashed 7/29.

If you flashed anything other than what I release like a kernel then you caused your own problem. Also. If you're getting reboots why not post a log? That way at least something might be able to be looked into. Otherwise it's on you guys to fix. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Superuser/root issue...?

Everything has been working great on latest releases with this rom..but just ran into a strange issue.

(first off...all my phones have been rooted and modded since day one..and have installed this and other flashes hundreds of times - so yes this phone is rooted)

i tried to sideload an apk today and Superuser acted like it wouldn't let me click "Allow" and then after 10-15 seconds or so a message comes up saying "it appears your device may not be rooted"...but it most certainly is.. i installed SuperSU but it would not get permission from Superuser to access...in fact anything new that i try to give access to with Superuser says access denied...but there are already some (root needed) apps installed and working fine...and in Superuser there are a few already showing as allowed and granted access...

This is the first time i've seen something like this on any of my rooted devices, especially after all seemed to be working fine for a while...

Any ideas or suggestions?

( i already searched this and the development thread of course to see if this was noticed by anyone else yet...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
I have always used Koontz' kernel and didn't have problems. I don't know if your room is the cause of the reboots but if it does happen again I'll post a log. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Just because you've always used a different kernel is irrelevant considering changes are constantly being made. In turn means that a kernel update is necessary. Both this ROM and kernel are updated appropriately. You will need to fix the issues yourself if you're using a 3rd party kernel. Wifi works great with what I packaged and released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tenchuu:
I experiment with Koontz' kernel as well, an gave up trying to flash it since i had the same no wifi issue as you. Sometimes these things don't play nice together, so i just left Task's Rom as is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
just to add...yes, *some*times KToonez kernel will have some random issues with Task's rom...I absolutely love KT kernel..thinks it's the best out there for hardware control and always try to run it..but on occaisional releases/updates of the kernel and/or ROM, yes they don't play well together" in those cases I have to ditch the kernel and use the stock from Task's rom..which is SOLID but doesn't have the hardware control that KT has..

outside of this...can anyone help or have any idea why out of the blue (on these latest Task releases) my phone would advise me or appear to be "not rooted" and deny access when it IS rooted and has been since purchase? have NEVER seen anything like this before..and it seemed that even after initial flashes of latest rom's that all was working fine...and now I can't sideload APK's or give certain apps SuperUser permission..even the general error comes up saying "it appears your device may not be rooted and root access is required"...very odd and no clue why or how to fix...anyone?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. You've just asked this. I'm sure someone will answer you when they have an answer. I have no clue as I've never seen it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
My phone isn't recognized by my computer, I have the latest Samsung drivers installed. Any help please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigbrd222:
From my experience, the drivers are pretty iffy. I had to remove and reinstall them a few times before it just worked. Try that or another computer if you have access to one. Also try using different ports.

By the way, this doesn't really have anything to do specifically with this ROM; you might want to search/post in the parent forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Mine does that sometimes too (on Mac and PC). Reboot to Download mode (where you odin). Once in Download Mode, hold down the power button until the device reboots.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No. I've answered this specifically about a million times. Samsung can suck it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm done with Samsung devices because they're all exactly the same. The sgs5 is an sgs4 with a heart rate monitor that I'd never use. Samsung can suck it because they can suck it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
So in how many ways are you wanting me to answer this dude? I DO NOT LIKE SAMSUNG. I THINK SAMSUNG SUCKS. I WILL NOT BUY OR SUPPORT ANY NEW SAMSUNG DEVICES. Back to this ROM please. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Um no. Its not hard to create custom Roms for their devices. I've been doing it for years. Not sure where you're getting this information but it sounds like you're just making things up at this point. I've already owned two sgs5's dude. They're called the sgs3 and sgs4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vbetts:
I'm running the 7/29 build, I thought I found my answer yesterday but I can't find it today! As far as kernels go, what kernels would work as far as functionality goes for everything? I've used Ktoons Tweaker on past builds and I love the kernel, but the build date of the kernel is older than the build date of the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Just look in the Dev section for other kernels if you don't wanna use the one Task packs with the ROM. There aren't that many choices, just go with what suits your needs. Their features are usually in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vbetts:
What I'm asking is if the 7/11 build of the 4.4.4 kernel my Ktoons will work on the 7/29 build of Task's Aokp release? Regarding, any new drivers that would conflict with the older kernel or not?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Wasn't so clear.

It does work but wifi doesn't until he updates it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vbetts:
What known kernels have the correct modules for the updated wifi driver then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
You gotta read man.

Every kernel with a release date close to or after Task's latest will have the right modules.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
I noticed the proximity sensor working for at least 20 sec. or so after display goes off. (Of course you have to be in the dark to see the glow) I didn't notice before flashing the latest of this rom, so I don't know if it's normal behavior. Is there any purpose/reason for that? I have lockscreen notifications off.

If you turn the display off with the sensor partially covered, you can keep it glowing as long as you keep your hand there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A Ham Sandwich:
I searched and couldn't find an answer.

There's an option in ROM Control, under Navigation Bar for "Long Action: Kill task"

Is this supposed to be the same as killing an application? It doesn't seem to be killing apps on my M8.

Clean install 8.10 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You don't need to kill apps. Linux does a great job of killing things when needed. But yes. It's the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A Ham Sandwich:
Thanks for replying.

I have an app that wants to stay running in the background but I only use it occasionally so I like to kill the app when I'm done with it. Using the Kill Task option from the navigation bar doesn't seem to close the app as the phone still shows the persistent icon in the notification bar at the top when I try it. It doesn't seem to do much more than go to the home screen. There's not toast popup saying it killed the app. The only way I can get the app to close out is by Force Closing it in the app info area.

I just wasn't sure if Kill Task was supposed to kill the app or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Builds 6/24-> 7/29 -> 8/10

I was running 6/24 for quite a while, pretty successfully.

After 7/29 I noticed that build, and installed it, over the 6/24. The Ribbon app from ROM Settings quit working. In fact, when I swipe to bring out the ribbon, I get "Unfortunately the process com.android.systemui has stopped.

Yesterday, I installed 8/10 over the 7/29. Ribbon still doesn't work, and I am also having a few other strange issues: Twice it has given me a message that my SIM had been uninstalled, and it rebooted. And right now as I write this, when I try to turn on the screen, I get just the lights for the soft buttons at the bottom and no screen, just black. I pulled battery and rebooted, and same thing.

My understanding is that it only requires a complete wipe if coming from other ROMS. I suspect what I'll hear here is that it is working fine, and I should do a complete wipe and reinstall.

But I thought I'd post about this just in case it is valuable information, and others having same issue. If a log is desired, I'll upload one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sounds like you might be causing your own issues by not fully wiping. Your understanding of when to fully wipe is incorrect. If you're having this many issues you would think the best thing to do is to wipe and start fresh. Also. I need as many logs as possible for this device considering I don't own it. Don't be afraid to post them. They're really easy to obtain and only take a few seconds. It never hurts to just post them regardless if any others are experiencing the same issue as you are. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ayeitschris:
anyone else experiencing the problem where the touchscreen stops working on 8/10 build? buttons and soft keys still works, just the screen will not respond to any touch.