yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wtcnbrwndo4u:
Hi Task,

I'm still getting complaints from friends about the in-call echo. Everything I've read in your changelogs or threads seems to indicate it has been fixed, but apparently it still happens. Any suggestions? I've done a full wipe/clean install, as I just switched over to AOKP from CM11 (where I also had the same problem).

Thanks,

wtcnbrwndo4u
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dfg187:
X2 anyone have a solution for this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
I fixed it by using a rooted file manager and searching for every file related to the app and then deleting them ALL and then reinstalling the app after a reboot.

As an example: To search for every file related to Kik use *Kik* for your search parameters, with the asterisks, and then proceed to delete every file/folder that is found... Then reboot and reinstall Kik.

I had to do this for three apps so far and it had worked every time.

WARNING: You WILL lose any and all data related to that app once you delete all the files!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] resrevni:
Kill All

Anyone else that's turned on the Navigation Bar seeing this behavior with Kill All when showing Recent Apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Just checked. This is what I see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] resrevni:
Well damn. I will fully wipe again and flash again. It's really odd. It's as if the Kill All button is underneath the Navigation Bar and only the top part is actionable. I appreciate the response, dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No problem. If worse come to worse and the wipe doesn't do the trick. Try changing the DPI to a little something smaller and see if maybe that'll help. I'm just taking a stab in the dark here though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leeroyjenks:
When updating form 5-4 to the most recent (5-19) rom I'm encountering issues. I keep getting "Unfortunately, google keyboard has stopped." I did some tests and it seems to only happen after the provided gapps are installed (5-4), as this does not occur without them. I'm trying a clean flash to see if it does the job. Just wondering if anyone has had the problem. I've searched the forum and found nothing, so thought I'd ask. If it persists, I will also provide a catlog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's really only 3 things that can be done even if someone else is experiencing this or not. Source doesn't get fixed by multiple users having the same issue. :)

1.) Fully wipe

2.) Provide a log

3.) Fix it yourself. (Most likely by fully wiping ;) )

So I would fully wipe first. I've personally tested this device before I even released and nothing of the sort has occurred. That's what tells me it only on your end. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leeroyjenks:
Figured as much I know you're always on top of things and this ROM is by far the least problematic out there. If anything does come up even after a full wipe I'll post back, but I doubt anything will. Thanks for staying on top of things and for the quick response!:cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Dont worry. A full wipe will fix you up. ;)

You're welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wtcnbrwndo4u:
Man, you're like the most attentive dev ever. You're awesome. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I try my best to stick around as much as possible. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
Hey task, I flashed your ROM 2 days ago and I can say I'm never going back to anything less! One "issue" I find is that whenever I press the power button to turn on the screen, it sometimes takes 3-5 seconds to actually turn on. I'm not sure if I can pull a logcat for that but my current setup is:

Your kernel

Min: 384 Max:1350

Interactive

TCP: reno

Everything else stock

I haven't even downloaded any apps, just the gapps you've put a link for. Any suggestions would be great ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
You're max Mhz is a bit low, therefor you gotta expect some lag.

I'd suggest trying another scheduler and see if that helps (ei: row). If not, you might wanna boost your max Mhz back up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
Still the same issue & tuned the max frequency back up. I tried all 4 of Task's bundled schedulers and still nothing. Could interactive be the issue? :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Try performance/row. If you still get it, the issue is somewhere else. Was it a clean flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
http://xdaforums.com/showthread.php?t=1756776

Will this kernel work with the 6.3 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Just look at the date. Nandroids are perfect for these types of things. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Asked first so I wouldn't have to do that (living life on the edge), and I was unsure if the latest build fit what KT looked to ask for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Backing up just the kernel takes about two seconds. Same goes for restoring just the kernel. No need to "live life on the edge". ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
A lot of people download on their phones. So I guess since you don't have the S3 you are incapable of understanding that the links don't work from the phone.

I'm really not sure why you are so hard headed and always think you are right. When clearly that's not the case all the time.

You get more donations with honey, much like the bees.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
[QRCODE][/QRCODE]

This ROM comes with a nice browser that works just like the one on most computers. If you don't want to use it then don't download the ROM. Its not that hard dude. I use g+ now. That's how it is and how its going to stay. Links work great and can be used from the browser. Pretty simple. Seems like it might be you that doesn't understand. I don't need an sgs3 to test links. I use the same browser on every device I own.

I don't do this for donations. So I'm not sure what kinda point you're trying to make here. Can you please drop it? You're not changing anything. Links will stay the same as they can be downloaded very easily from mobile or computer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordonson:
The search function and Google haven't seemed to be able to lead me to an answer here (unless I have been searching the wrong terms), so I hope you'll forgive me, as this may not be an issue exclusive to this ROM.

I came to this ROM from a 4.2 ROM and at that point I know Flash was already no longer supported, but I was still able to at least see embedded YouTube videos on sites and either play them there or go to the dedicated app. Now those videos, or I should say where they are supposed to be; are just blank spaces. This happens in both the stock browser and Google Chrome. Did this happen across the board for 4.4+ devices or is that just something that comes as a price for using this beautiful ROM?

I apologize if my question is stupid as I am a bit of the loop clearly, but I appreciate any insight anyone can offer. As mentioned, I'm loving this ROM outside of that one matter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
It's not ROM related, although, you can use Dolphin browser with jetpack to have flash support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordonson:
Thank you very much for assisting me, and I apologize to Task650 for asking this here then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] In3rDm0RetHeNu:
I'm on a fresh install and I'm having problems calling people. Majority of the time it doesn't call them, it doesn't ring or anything. Also, the preferred network type switches by itself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
My network type resets to default LTE/GSM/WCDMA after every reboot but it literally takes two seconds to switch it back so not a deal breaker of any sort
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All those network overlays will not apply anymore as they have been removed. Next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
factory/reset, wiped cache+dalvik , mounted /system+ format system

installed aokp+ Gapp provided provided with rom.

AOKP 4.4.2 KitKat Build 6.3.2014

NEW!Gapps for KitKat (4.4.2) 5.4.2014

the phone is clumsy.. sluggish. everything is slow... i keep getting "this app won't run unless you update google play" messages.

flashed multiple times. downloaded both rom and Gapp packages.. still same issue.. something doesnt feel right... anybody had this issue and a way to fix it?

btw i heard ktoonez kernel is not working anymore... is there other kernel that are working with your ROM so i could overclock it a little to give it some kick?

edit: by the time i wrote this there is an update 6.8.2014..

edit2: still getting the "this app won't run unless you update google play" messages.

fix:for some reason i needed to install Google play Services from the online play store

https://play.google.com/store/apps/details?id=com.google.android.gms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
The stock camera (not google camera) FC with this ROM. I clean flashed 4.4.3 build, and I noticed the same even earlier versions too.

Is this known issue. or do I have to do something to use stock camera?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's because the AOSP camera is not included in this ROM anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You didn't need to install it. You needed to update it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Thanx Task for quick reply. Yes, I thought something similar. as I dont see the app in the list, but using Nova launcher, by default shows stock camera on Dock, which is what I was trying to open.

I like everything with Google Camera, except, the ability to use SDcard as storage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's a deal with Nova Launcher. I can't change anything in regards to that app. Use and exposed module if you want to save to external. Just search Google or XDA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Absolutely agree. I was just making point about Nova Launcher, why I was seeing that issue.

About xposed, good idea, didnt think of it :)

Just wondering, other than these AOKP based ROMs development, (if u dont mind asking) what do u do. Android developer ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Doing online sales at the moment due to my last employer (I was a GM at a high rise window company) turning into a ****. I've never had any software or development jobs. I just got into this kinda stuff years back and decided to put myself through school to get another degree so I could be decent at my hobby. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Reason for asking the question :- If you are not in school now, and are good at android development (not sure, what level of android expertise u have to put while building these ROMS), i might refer u at Yahoo. Just let me know, if u want to pursue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It all would depend on what the position is. I wouldn't really want to ruin the fun in my hobby by turning it into a job. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
You can look at all android apps developed by Yahoo Inc. In the same line, either enhancing those existing apps or developing new apps at industry standards. If you are interested, plz send me ur resume, I will fwd it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
Wondering if anyone has noticed something I noticed the past few days. When the car Bluetooth connects sometimes the phone screen will not turn off. If i turn the screen off manually, the screen turns back on in a couple seconds. If i turn off Bluetooth, the screen works normally. Running a clean install of the 6-8 version. I found the correlation today when I looked at BBS and noticed a Bluetooth wakelock (though I can't remember the specifics) ill try and get some useful data tomorrow. Just wondered if this has been reported already?

Thanks for the work Task.

-J
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You could just look through the posts since the last release to see if it was reported. There's only been a couple posts since then. Any other release prior doesn't matter as they are outdated and unsupported.

You're welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
Logcat attached. I started catlog and started the car. Bluetooth autoconnects and screen turns on. I then manually turned off the screen and a few seconds later it comes on by itself.

Let me know if you need any more information.

Thanks Task.

-J
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobamoba:
Yesterday, my calendar notification (which is default everything) went on an endless repeat loop and wouldn't stop. The only way to get the sound to go away from to reboot the phone. Other notifications work fine. Any thoughts about why that happened or how to prevent it from happening again? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Can I change the intensity of the haptic vibrations for the buttons?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Has anyone successfully used Quantum kernel with this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I have been getting some random SoD's and reboots from time to time, on both the 6-8 and 6-17 release. Using the provided Gapps and the kernel packaged with the rom. Kernel settings = Ondemand/Row, everything else stock. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Suggestion would be to provide a log so it Can be looked into and maybe fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Hey Task,

Could you add

getprop("ro.product.device") == "d2can" || getprop("ro.build.product") == "d2can" ||

to your updater-script for the d2lte?

Would save us, Canadian users, the trouble of adding it for every release.

Thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi. The OTG adapter work. With this ROM?

---------- Post added at 08:44 PM ---------- Previous post was at 08:37 PM ----------

OK not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Is the latest release stable? Planning to pair with ktoonsez kernel for dat batteryz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not sure why anyone would release an unstable ROM here other than for development purposes. There's a major difference between having bugs and being unstable. You should have a nandroid. Flash it and see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seboj:
Data symbols staying gray

Thanks for all your hard work Task, your ROMs are always solid.

I updated to your KitKat 6.19.2014 earlier today, and I noticed that my network and wifi symbols haven't changed from gray to blue, showing connection to Google servers (item #16 on post 1). I installed using the latest TWRP, factory reset, installed ROM and GAPPS, everything went fine. As far as I can tell, everything is working OK - I don't have any problems using Google Play Apps. I updated the APN to LTE. I wiped and reflashed everything when I got home, but it still acts the same.

I haven't seen anything mentioned in the changelog or the dev thread about it. Did I perhaps miss a setting somewhere, or maybe they don't change anymore and I'm being daft?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nothing changes to blue in the status bar. This is KitKat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Lightflow -> 6/17 build

I've tried various settings, and am not having luck with LIghtflow.

As well, I've tried testing the LEDs through the LED secdtion in Rom Control. Doesn't work.

Is LED not functional currently on this? Any suggestions appreciated.

By the way, the LED DOES come on when charging.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Installed newest ROM today...

I have used your ROMs for my S3 phone exclusively for a lonnnng time now. I think yours is the best. I typically use for months before jumping up a version or release(s)

Anyways this is basically to see if possible known issue or if (what i already think is likely culprit) causing problem and if so..just say so and I re-flash.

Anyways, the surface level sensor has problem.

All other sensor tests (seem) to be ok..and phone can detect portrait/landscape but apps like Screebl can't tell if phone upright or on angle...so used smart tools to test as well and surface level has no response too.

Is this likely Kernel or ROM? I unfortunately just did install today of both ROM/kernel but didn't find out or test to see if this issue came with new ROM install or with kernel...I did use this fresh for about half hour before KToonez kernel flash and believe it (may) have had issue already but uncertain.

Just thought I'd ask first before any re-flashes or recovery and if u think its definitely the kernel (which I assume likely too) then my apologies and disregard and I'll reflash..your kernel is fine anyways and have used for long time but wanted to give an OC'able kernel a try again this time...but no biggie..

Thanks and aside from this..everything looks and seems to be working amazing!

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I just flashed 6/19 everything workin great except the compass and the GPS is there anything I should do please help needed.

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
How do you unlink Ringer and Notifications volumes?
[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.

The sensor that detects and measures surface level does not work after coming from 4.3 to this 4.4 KK (full system/data wipe etc)

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 do u think?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please stop posting the same thing in both threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please stop posting the same thing in both threads. I've already answered you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
https://github.com/task650/device_d2lte/commit/b23b9e5e5378e3cc215161c0b748e50f1820de9c
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Any feedback on Lightflow?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sarfie:
Just flashed this on my wife's s3 everything seems to work great other then the browser. Get a net::ERR_EMPTY_RESPONSE. Any fix for this I downloaded chrome for the time being and it's working. Also if I click the ROM control app in the drawer it says asp not installed. I am new to aokp so sorry for my ignorance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nationalicon:
I got around this by flashing the d2att version of TWRP on my d2can phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This post has already been responded to. There's no need for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nationalicon:
USB OTG adapter works fine for me, using a bluetooth mouse and dongle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
The Bluetooth work with Bluetooth setting on the phone not with USB otg... in my case only USB keyboard not USB flash drive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gsm22:
Hey task650, love your ROM and the work you put into it, I've been using it since I first got my S3 last year.

However, there's a problem I've been having with audio/sound in the releases that came after 3/13/2013. Simply put, all audio (including volume adjustment sounds) refuse to work at all. I always double check the quiet hours and relevant settings in the Settings menu, but this usually does nothing since the sound is screwed from initial setup after a clean flash. (no key sounds or lock noise, volume adjustment sound, etc)

A search of the i747 forums turned up one other person who had similar problems with KitKat roms: http://xdaforums.com/showthread.php?t=2723252

Unfortunately none of the suggested solutions worked for me, as I'd been following the same procedures for a clean flash like the OP did.

I've tried almost everything to try to fix it on my own:

- Updating bootloader to the one recommended in the Q&A thread (I747UCDLK3), and then trying almost every one of your releases since 3/13/2013

- Rebooting with and without cache/dalvik wipes after clean flashing the ROM

- Updating bootloader to I747UCUEMJB (this was necessary to get back to stock)

- Flashing AT&T stock firmware 4.3/4.4 via Odin (these had working audio)

After seeing that stock firmware had working audio, I decided to try and clean flash your latest build with both the latest CWM and TWRP. Neither of these yielded positive results :(

I know I might be asking a lot from you since this problem seems to be limited to a handful (if that) of S3 owners, but if you could look into it, I would be really grateful. I've made a logcat for you to look at; specific lines seemed to pop up when I used a volume key with volume adjustment sounds enabled.

Thanks again for the hard work you put into this ROM, looking forward to hearing back from you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Love the ROM, except I just can't get any LED notifications.

Per my earlier post, LIght flow doesn't work; the LED notifications per ROM settings doesn't work; just tried Light Manager, and that doesn't work either.

Been watching for an update...hoping the next one will fix this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
That is most likely on your side. It's working just fine here.

Did you clean flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Good to know it's working for someone.

Yes, I did clean flash.

I wonder if I can just re-flash the ROM over it now, without doing a reset of all, and that would help. I guess I could try it.

Resetting everything on the phone is a pretty long task for me.

Thanks for the reply. At least I know it works for someone.

[EDIT}

Can you share what settings you need to use for LF? It seems that every version of Android requires some different settings, in different places, for LF to work. Maybe I'm missing something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
LF being Light Flow?

I don't use it. I use what comes cooked in the ROM, stock settings.

You could try a dirty flash but 3rd party apks aren't affected by that and aren't supported by Task (he supports what comes with the ROM). It would be up to LF's dev to make an update to work in this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I couldn't get the cooked in stuff to work either. I will likely need to try another clean flash.

Interestingly, I did just go in and turn on something about 'pulse led'. Now I can't find it :rolleyes: ... but I'm getting light flow started, l believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Settings/ROM Control/LED
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
No. Just did find it again,and it's in Display/Pulse Notification Light.

The reason I said 'Interestingly', is because earlier in this thread (I do try searching :) ) someone had to turn that off to get LF (Lightflow) working, albeit, that was a different ROM version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredor:
Jawbone UP Sync

Has anyone else had issues syncing a Jawbone UP through the audio jack with this ROM? Pretty obscure question, but I wanted to see if I was alone. My apologies.