yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Not Omni...ElGoog!!! Good one task :D hope you are well. I'm running with the stock kernel and my 64gb exfat microsd isn't working at all, dealt with it before but never been stumped like I am. Have tried init.d script, a flashable lib file, etc. I don't know if flashing another kernel is the best idea, I assume they need to update to 4.4.2 but I will still make a backup and try. Maybe you have an idea though. I'll update if I find my solution
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Celidonius:
This is the first time I've ever been so confused and frustrated trying to install a rom..

After doing a complete wipe, the phone just reboots into TWRP..

Any one else experience this?

I was running the latest quantum rom, then wiped everything, then flashed task650 successfully but phone keep booting into recovery mode (TWRP).

Any help? I feel so stupid for not knowing what's wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I was going to give this a try, but I can't get the AOKP Gapps to flash, getting an error 7. I'm using CWM and saw somewhere that TWRP is recommended. I've tried downloading and flashing three or four times with the same issue. Do I need to do something different?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Use twrp recovery...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Use a different gapps then. Alos use TWRP recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Ok. I didn't know if there was anything specific about this Gapps package, since the installation instructions are pretty emphatic, "Use the gapps package that I provide in this thread!" Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Only bug I encounter in 4.4.3 version is Dialer not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's something on your end. I was around an s3 running this ROM all day yesterday with it working just as it should. Also. Screenshots of force closes are not useful at all. They show nothing about an issue.

P.S- Don't use that theme. Bet it works just fine after you do that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Oh thank you, I never though it would be the theme. I set it to Holo and now it works.

Edit- Themes are not yet updated to work in 4.4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
The dialer is new in 4.4.3, so most themes don't play nice with the new dialer yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Themes have nothing to do with this ROM. It just has the engine for them to be able to be used. You have to go and ask whoever creates the themes to update them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi task650 thanks for this ROM I all ready flash today and I said GOOD!! Congratulation for your work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Ok, yes I understand. Since the dialer is diferent, the creator of the theme must update it for it to work in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josue276:
could put the new Hover notification system that has PA in its most recent version. I would appreciate. I talk about this: http://youtu.be/u_3Ik7m3z50
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JustAnotherCider:
Maybe your *gigantic* signature is wrong, but you might be in the wrong forum? This is for the galaxy s3 not the s4 :p.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] josue276:
lol my signature is that S4 was damage and get me back to S3 i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please read the OP before posting here. There's a dedicated thread for posts like this. Please use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
Haha!! He's posting the exact same thing in several different ROM threads... If it's so "must have", I'm not sure why he just doesn't flash the ROM that it is in. :confused: :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is a development thread for this ROM dude. Go start a thread in the Q & A or General section of the forum if you want others opinions and call AT&T if you have questions about their upgrade pricing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Task has said a bunch that he went with the M8 over the S5. That's what he'll be developing for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available in the OP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Thank you TASK! For the update, I was loving the 4.4.3 performance this ROM was giving to my phone.

:( I got excited for the update and do not know why when doing full wipe my phone turned off and now is soft bricked... ( I had full battery charge)

Well for now will be downloading stock UCUEMJB.tar to flash phone to stock. Man my internet connection is so slow 5 hours to download that.

Edit- Hardbricked phone after flashing stock mjb using ODIN.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi. USB storage not work on this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please read the OP before posting here. Thanks.

This is very conveniently link in it.

http://xdaforums.com/showthread.php?t=1781242
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
OTG not Work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Well seems like logcat is as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] murayoshi:
can you flash this on tmo t999 it sez unified
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Read the OP. You're in the wrong thread. This is a development thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
My cat has lots of logs :good: :highfive: :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yuck! Nice dude. :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Ok check the logcat..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's a way to ask and a way to tell someone. Think about it a little dude. :)

If I remember correctly. OTG is taken care of on the kernel end. I'm not providing a custom kernel for this ROM. So you're outta luck unless you flash a kernel. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Maybe the logcat not for you but for somebody to ask for logcat but its OK and thank for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I need logs for almost all issues for this device. Otherwise they will not get fixed in my source. And in turn doesn't get fixed in this ROM. ;)

Like I said prior, try a different kernel dude. See if that's works. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Its called SWAGGER MODE. try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
task English is clearly not his best language lol! thanks for the new release.... and to people who maybe wonder yes it works with kt747 just like the old days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
The June 17th build is stable, right? Planning to pair it with ktoonsez for dat battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release is up guys. Check the OP for ROM/Gapps. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
what the... that was unusually quick! fingers crossed I can find a fix for exfat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zinnz:
Only a day after I even knew 4.4.4 was captured.

Thank you for the weeklies, or in this case 2 days :D

I'm loving how smooth everything updates and runs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I installed this rom and so far so good. I have some questions though.

First: How do I separate notification and alert volume?

Second: Music effects stops when I try to access it.

Third: Double tapping the screen or app makes the screen zoom and a blue border shows.

Any help would be greatly appreciated. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
I did look at the OP of the Q & A thread but couldn't find the answer. Love the Rom so far. BTW, ktoonsez kernel and your Rom go together like pie ala mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
What version of Kt747 did you flash? I don't know which one's compatible with AOKP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
KK AOSP 6/1 version is the kernel I installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
You're asking questions in the development thread. I'd suggest posting questions you want answers to in the Q&A thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Here a screenshot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
OK have now done a fresh wipe n flash of this ROM with stock kernel and still same sensor issue so its not the ktoonez kernel.

So the sensor that detects and measures surface level does not work after coming from 4.3 to KK.

And just to be certain..have flashed on both a 747m and 747 (yes a true AT&T model) and same issue on both..

Am I missing something or what u think?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're missing a log as none of these posts do anything in terms of helping to troubleshoot. Logcat or it didn't happen dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What's the point of this screenshot? Seems like I'm missing something here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
It's just t show that I have your rom and ktoonsez kernel working together. In your earlier post, you said that as far as you know, it did not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
very true...I know..I was more or less just asking if you knew or anyone else was reporting this.

I have since (very temporarily) installed latest CM to test...and IT DID work fine. .so it is the ROM on both my Rogers and AT&T phones...

As I stated...I prefer and exclusively use only your ROM on my S3's...nothing against CM...but not my favorite..so I would love to have your ROM fully working on my phone..

I will reflash a completely wiped and fresh brand new install of your ROM and get the logcat right from brand new install..

so I take it..no one else reporting this yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This still doesn't help. You can search to see what others are reporting. So how many more posts until you actually post the log? This has been drug out long enough I would think. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
ok..fair enough..was just asking...

anything different about the logcat because this isn't an "error" or a "crash". it's just an issue where sensor (only one and only part of) doesn't seem to function..i would have guess kernel or firmware as that is what causes hardware issues but KK 4.4.4 of others and with KT kernel works ok.. so just typical logcat?

Thanks and sorry to be a bother
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Don't worry about it. I took it in my own hands and high jacked an s3. I really just need the logcats for these issues to fix them unless its something upstream that needs to be fixed as I rarely am able to get my hands on this device. So for next time when you encounter and issue just pull a log and post it here. All the info you need to know about reporting bugs is there the FAQ. Least that could happen is nothing shows that would help. They only take a few seconds to take. No harm done. ;)

What the the problem you were having anyways?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's no need to link you to something that is very clearly linked in the OP in the first couple sentences of it. All the info you need is there. There's a whole section on how to logcat and submit bug reports. Just read the OP dude.

Edit: I just checked myself and I'm not seeing the issue. I opened the dialer, pushed the 10-dot symbol (it opened the dialer), I made the call, the call was great. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greysonofusa:
Great job task650! :D

Literally the best ROM I've used yet. Used to run liquidsmooth for years but now I'm strictly task650.

I am thinking of getting a galaxy s5 any chance you will develop for the at&t version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Try again then dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release is available. Check the OP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ffinger:
Newb sorry

Hello I recently rooted and installed recovery on my wife's S3 Model number SGH-i747M I searched the thread and havent found a definitive answer.Just want to know if the latest rom and Gapps package work on the 'M' variant. As far as i can tell the ATT phone and telus are the same. Just want to make sure. The wife just gave me the go ahead to root and rom her phone. I can use odin and have a bumbling knowledge base with android coming from s2x and currently on an s5. please bear with me as i am sure this question has been asked and answered a zillion times. i just could not find the answer. thank you in advance for and feedback.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zinnz:
Thankyou for breathing life into our s3s!

My phone runs smoother than my gfs m7, HTC or Samsung should definitely hire you.

I tip my little pink pimp hat in my status bar to you. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release has been taken down. Need to look into somethin. I'll post when its back up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release is up guys. Check the OP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leeroyjenks:
I've been having problems with the network since a few builds ago, both on clean and dirty installs. The network will randomly completely drop and take a minute or two to come back. It happens very often. I have the S3. I know task doesn't have the s3 anymore so I was wondering if anyone has the same problem. I've attached a screenshot of the logcat when the event occurs. If task would like I can post a full logcat.

Task I'll post my apology ahead of time if this belongs in the Q&A thread. Figured since I have logcat info it may help.

Thanks for a great rom!

Edit:trying to post image from xda app on my phone bare with me.

Sent from awesomeness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Always post with the logs you guys grab. It never hurts to post them. That way if something is caught it can be seen. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leeroyjenks:
Thanks again! Trying my best to upload image and/or logcat. This app is subpar. If it doesn't work I'll host it and post links.

Edit: stupid xda app

https://www.dropbox.com/s/912naetb85mnkup/2014-06-25-17-21-02.txt

Image:

https://www.dropbox.com/s/i46cw51e348tgjo/Screenshot_2014-06-25-17-35-09.png
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abomb78:
Any chance to get the option to turn on or off the "auto screen off during calls" in the call settings menu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I have no clue what that even is. So probably not. If you can link me to the commits on github or gerrit I can check them out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Task the moment I saw that picture of your phone with the Linux terminal building "something"... I just stopped trying to fix the problems I'm having and sat back for the next release.

I'm not sure if it's hardware or what but sdcards do not get read. Exfat 64gb, FAT32 33gb and 8gb I think.

Thank you for the new release. I always get gaps errors and **** on boot so I think I'm gonna try 0day happy. Either way nandroid right now qq later, wish me luck and thanks again.... May be able to donate some more soon.

---------- Post added at 02:02 AM ---------- Previous post was at 01:48 AM ----------

Never seen that in any ron settings what is it from? Carbon? PA? Slim? Either way it's just a setting for the proximity sensor.

Put this into your build.prop

First make sure proximity sensor is enabled:
gsm.proximity.enable=true
ro.lge.proximity.delay=25
mot.proximity.delay=25

This makes the proximity sensor in the front of your phone which determines if it's touching your face or not (hence in a call and turns the screen off)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abomb78:
It was under the call settings in the stock android 4.3 update. I would just uncheck the 'auto screen off during calls' and I can access my phone to look up some bit of information while someone was on the other line. Currently I just have a blank screen as soon as I make a call even if I try to hit the home or power buttons to turn the screen back on. I would assume that it would be an established set of coding being on the stock ATT Android 4.3 build. But I know what assuming can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please go post in the General or Q & A section as none of this has anything to do with this thread or its purpose. Also just about everything has been answered already. Just run a quick search on XDA or Google like you're supposed to do. :)

I've linked you to and put up screenshots showing you the link in the OP for a dedicated thread where the non relevant to development posts go a ton of times before. Not sure what the problem is. But I'll try again. Go here dude http://xdaforums.com/showthread.php?t=1781242 .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
Heads up notification :thumbup::):)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Very minor thing, but it seems wifi doesn't automatically turn back on when you turn off wifi tethering. It can be turned back on manually without issue, but it's not typically a necessary step. Otherwise everything is superb though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You haven't reported a bug until you've posted with a logcat. Without a log you'll have to fix this on your own. I don't own this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Sorry, didn't think this type of issue necessarily warranted one. Thought it was more for crashes, and things breaking. Thought my issue was more of a setting not implemented properly, or a simple coding error on the back end. I don't know how any of this stuff works though, so duly noted. I'll look at getting one next chance I get.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If your WiFi isn't turning back on after turning tethering off then something could be broken. That's why hopefully a log when its happening will show the cause. Without having the device I can't pull any myself. Tested on my device (m8) and it worked fine. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterKoala:
Something wrong with this rom i guess ? Because The antutu score is soooo bad... like 8k and the Gpu performance is really lower then the stock 4.4.2 kitkat rom. might be a gpu driver issue i guess. because normally antutu gives me like 18.000 points and this rom get me only 7,9k points and the FPS rate at the OpenGL ES 2.0 test was really low. at the stock and slimkat rom fps rate was 25-30 but with this one it is 7-10 ...

Meybe the developer needs to check it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattio781:
Log cat or it didn't happen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I can't check an antutu score on a device I don't own. What issues are you encountering? Does it feel that slow? What kind of data/logs have you gotten (other than a benchmark)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Using antutu benchmarks to rate a rom is absolutely ridiculous. Using antutu benchmarks period is ridiculous. They are about as useful as putting nitrogen in your car tires. Or referencing a global average temperature. Or referencing wind chill or humidex to determine temperature. All these things have something in common.... They are all useless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
THANKS!

Just wanted to say thanks for the great ROM. I just stumbled across it and installed the 6/28 build and gapps last night. It fixes nearly all the issues I've had with other 4.4.x ROMs.

One issue that I still have is most embedded images in Gmail are not loading properly, but I think that's a universal issue with Gmail at the moment. The other issue was the stock kernel seemed to really bog down the device. I flashed Quantum 6.28 and all is good now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
Re: my earlier mentioned issue of Wi-Fi not automatically turning back on for me after tethering, here's a log that hopefully might show something useful. If I recall, I did turn wifi back on manually before the end of the log.

Thanks.

https://db.tt/G34ubO5n
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
This latest version is working great! Task's tweaks and fixes are always on point, I'm amazed by his attention to detail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterKoala:
İ have a logcat and i searched for gpu logs but there was only software rendering. No hardware (gpu) rendering at all. I run different tests. The basic structure of the rom works fine but gpu is not working at all. Now changed to cm 11 and logcat shows that there is gpu rendering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Over the weekend I had some wicked fast LTE (vzw) with this ROM. Had to share.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you have logs that you think will help just post them. You still haven't even said what issues or errors you're experiencing or have found? Benchmark scores aren't even worth a penny in terms of troubleshooting.

If the GPU were broken/not working your device would most likely not even boot. It could just start up and shut down itself repeatedly and might get artifacts or weird colors on the screen. In short. If the GPU wasn't working then you most likely wouldn't be able to even run a benchmark let alone use the device. Word of advice. Don't rely so much on benchmarks. Especially on android devices. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MasterKoala:
I know the structure of the roms and kernels. There isnt a driver for gpu on the rom that we are talking about. You may dont know but these things are really similar to the pc. E.g. if you dont have your vga card driver installed on your pc. İt loads a defaulf driver to boot up and shows you the screen. This has the exactly the same problem. Check the rendering libs and you will find your problem there. Rom can do the basic prosses but cant make a gpu rendering. Because it hast got a driver in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
I'm using the 6/29 PA Gapps and am getting a nasty wakelock by Google System Update Service. Apparently CM has a fix in place. Will this get merged into this ROM or no because this is AOKP and not CM?

http://review.cyanogenmod.org/#/c/66894/

Thanks again for the fantastic ROM. It's by far the best 4.4.x ROM I've ran so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Days ago https://github.com/task650/vendor_task650/commit/a3ab7488d50abd45e17b3f0280f5113df499e6f8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Right on, thanks!

So the fix isn't in the 6/28 release, but will be in the next one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
I try other roms and always endup comming to this one... Is still my favorite. By far the best, performance and battery life... And somehow even faster in data speeds than stock or any other.

I lost my previous copy of the rom which was running perfect, will wait for the next version to install it.

Aokp in SGS3 is like Super saiyan mode :)