yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Follow my steps posted here.

http://xdaforums.com/showthread.php?p=29786623

---------- Post added at 04:16 AM ---------- Previous post was at 04:12 AM ----------

Haters always gonna hate... and if u look at their profile they got a ton of posts and almost no thanks... I'll pm u my gtalk... I'm always willing to help man....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o57marthas:
I've been on 8/17 aokp, today I flashed 8/20 after clearing cache and dalvik, everything is working great except that I normally need to change my fonts again. I use Font Installer. When I opened it there were no fonts. I tried to reinstall from play store and still no fonts. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
HW overlay is not supposed to stick on reboot. If you want to make a script to re-enable it on boot.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Well unfortunately that's something task would tell you to take up w/ the developer. Can you humor me and explain your version of wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
I'm also having trouble getting settings (like governor) to stick in Rom Settings. This is after a full wipe. Maybe I'll try clearing data on Rom Settings or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Well keep in mind, you should be doing a complete wipe and format of system between each new rom... This clears all those settings out. The reason for those wipes is to prevent carry over from one rom to the next. Until this is a RC it will always be that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o57marthas:
all that I did on this one was clear cache and dalvik, I'll just try a full system wipe. I was just wondering if anyone had ever experienced something like that. There don't seem to be any other issues I didn't want to do a full wipe for just fonts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Bro... still right there in OP it states Complete wipe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Okay so I know Google Now and voice to text is working fine for you task...but for me after flashing after a full wipe: data/cache/format system/dalvik. I installed your ROM and gapps. As soon as phone booted I went into messaging and tried using voice to text. It caught the first 4 words I said then stopped and I had to push the circle to start speaking again. It didn't stop because I stopped talking btw, I was reading a sentence normally from some web article. This is really frustrating as I use this feature all the time and I LOVE the ROM. Is anybody else experiencing this? It worked fine on ICS builds of AOKP, the voice to text that is.

Sent from my Tablet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
What do ICS builds have to do with this ROM? This is Jellybean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You didn't follow the installation instructions. Please don't post "bugs" until you do. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] o57marthas:
I never said or thought it was a bug. I know that it's local to the device. I'm not an expert but I've been doing tech support and flashing custom roms long enough to know that there could be an easy way to fix this other than doing a complete wipe. I've been on xda for a while. This is supposed to be a community. Yeah, I could have done spent time doing a Google search or searching all of the forums for a resolution but I know that people spend a lot of time on xda and other forums. I thought this forum was the kind of place people could go to for help. Someone could have just said I'm not sure try searching q and a at some link or another. That's friendly support and all that I was looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
i said it once. now here's twice. DO NOT POST HERE UNTIL YOU FOLLOW THE INSTALLATION INSTRUCTIONS. they are there for great reasons. it does not matter how long you've been flashing or how long you've been on XDA. it's just that simple.

P.S- Your expectations of what others or how others should have responded do not belong here. I was actually really nice to you. I even said please and thank you. read it again dude. Please do not post here anymore. thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
YES! Finally got to installing this latest rom and the flickering was buggin me.. Thanks Tasque! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
What I was trying to point out was that it wasn't my phone that was defective. I also noticed a user had the same issue as me and he gave me a guide you gave him to try and fix it which I am trying out now, I will finish this post when I finish up reflashing here.

Okay so that worked. I redownloaded the ROM and gapps on my pc and then transfered to my gs3 and then booted into recovery, wiped everything including data/cache/format system/dalvik and then rebooted into recovery and re-wiped everything again and reflashed the rom. I just tested out my messaging app and it can hold and listen to everything I say....thanks!!

Wonder what caused this? Since 2 confirmed people have this bug I'm sure others do as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
2 out of over a thousand isn't bad odds. gapps probably didnt fully flash. it is a pretty well known thing that gapps has to be flashed twice sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Yes, TiBu wipe data for all respective CPU control apps... Use Voltage Control or SetCPU... I've had issues with the Performance section of ROM Control that I could probably fix, but I'm lazy...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Task: Thanks again for the work!

Anybody: Just want to make sure I'm not crazy (or at least more so than usual) :cyclops:. Searched Q&A, FAQ and some other acronyms I can't remember....but couldn't find a definitive answer.

Is it normal, using a file explorer (ES File Explorer in this case), for me to be able to "see" or "get to" my External SD card through 3 different paths?

/external_sd

/mnt/external_sd

/storage/sdcard1

Just trying to make sure I don't have something wrong I need to address. Or, is this just part of the whole "there are issues with the way JB looks at storage and they're being worked on" thang? :D

Thanks for any input!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
That's normal... different parts of the Android OS use those paths as references for access to the card....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
Hey Task keep up the great work. Love the rom. You feed my flashing addiction. Here's a little something.

5RV73278DR033841W
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
What exactly does disabling HW overlays do? Besides fix the screen flickering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
I also found that i get no more random reboots

http://en.m.wikipedia.org/wiki/Hardware_overlay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
This ^

I think this basically disables project butter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
A few googles give me this:

[Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.

Basically, using hardware overlays can reduce CPU usage by quite a bit, so I would leave it enabled. ]

[Disable it and the latency period for applications and the OS (any OS, not just Android) itself to render things will go way way up because it has to check to make sure it's not screwing with memory that is supposed to be dedicated to another task than its own. Hardware overlay ensures everyone has their own partition of memory so they don't have to do those checks and so latency to render things on the screen decreases dramatically.]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
Got Underwear?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
I posted this on the CM10 thread but Hardware Overlays is not Project Butter as I understand it:

I could be wrong and correct me if I am. But I dont think Project Butter is only about how hardware overlays are used, Disabling it only offloads the processing to the GPU rather then CPU. Also yes our phone has the best Dual Core Cpu atm but our GPU blows in comparison to the Mali GPU the international variant has..Anyway here's what I understand of Project Butter and Overlays.

Hardware overlays prevent applications from sharing video memory..Without it every application that is displaying something on the screen will share video memory.. This causes the app to have to constantly check for collision and clipping before it can render the image onscreen properly. This can lead to a lot of processing power being used. With a hardware overlay each application gets its own portion of video memory, Therefore the app doesnt need to always check for collision and clipping before displaying the image.

In short the use of hardware overlays can reduce CPU Usage significantly.

As I understand it Project Butter is a combination of the use of Vsync, Parallel Processing and Triple Buffering, Vsync reduces frame tearing.

Vsync prevents the same frame that was previously shown to be shown again..This contributes to the Jank/Stutter we see in many Android devices..

Now onto buffering, In a normal android setup Double Buffering is used, these buffers contain the frames that are built then displayed.

Example: with double buffering 1 frame can be displayed while working on another. While displaying buffer 1, the system starts building a new frame in buffer 2. When its complete, the buffers swap. 2 gets displayed, and 1 gets cleared and a new frame is worked on. This can be a problem if one frame takes too long to draw, this leads to time being wasted, this creates a problem where the two buffers become unuseable...the visual result is again stuttering/choppiness..

In Jellybean the cpu/gpu has 3 buffers to work with instead of 2, How does this help solve the problem, well when the same problem occurs with the first 2 buffers the system creates a third buffer to process the next frame in line. Now there is a drawback to triple buffering it creates a bit of lag during the Frame rendering process...So we have a choice its either stuttering and choppiness or slight input lag...

It is this reason that Jelly Bean does not always draw on triple buffering...JB uses a normal 2 buffer set up most of the time but when things do go awry under the hood it falls back on that 3rd buffer...this means less input lag than if you were to use triple buffering always...

Again if I'm wrong correct me and sorry for the wall of text.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
I am not using any of those apps, I was hoping to use the Rom Control module which doesn't seem to be saving the settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
unfortunately if its not working for you the next best step would be to use voltage control. its what i use and have no issues with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 613BulletProof:
I updated to the latest build of this Rom..

I did a full wipe data/ wipe cache / wipe dalvik

Flashed latest rom, flashed stock kernel, flashed Gapps

Everything seems fine but my Gapps are still the same, the backgrounds arent gray/black (gmail, messages etc)

I tried going into Settings> Apps> and clearing data for Gmail and Google Framework Services, rebooting into recovery, then reinstalling Gapps again and still did not work.

I had it working perfectly fine on the previous builds. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) No need to flash the stock kernel from the OP. That kernel is what is already packaged with this rom.

2.) The gapps package from the OP does not come with grey/black gapps. They are just the standard supported gapps for this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You're installing gapps instead of the inverted gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Searched but not 100% sure I saw a definitive answer....LED's working 100% correct for anybody? (ie, all missed events notify, colors accurate, etc) Looks like it's still in the works, but didn't want to assume I was doing all that I should/could. (mine don't seem to be consistent....And didn't want to bother with Light flow yet). :D

Outside of that, loving the beans!:thumbup:

Thanks for any input!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryandelman:
Really not much bother to Light Flow. Takes about 10sec to install and about a min or less to customize.

Just saying.....

-Ryan
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I have no issues with led. Works %100 for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
I'll take that into consideration. ;)

So, to answer my original question, that mean the inconsistency I'm seeing with LED on stock AOKP is normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
So out of no where it started doing the same thing again. It would stop listening after 3 words or so. I was just driving and texting my girlfriend back and forth and all of a sudden now, even on wifi, it does that.

I just re-did the method posted earlier and reflashed everything hoping it to stick this time. Is there anything I can do to help you figure out what is causing this?

Sent from my Tablet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electronics18:
Like Task, mine work 100%, colors are accurate (same as Light Flow, some limitations with the mixing LEDs for some of the colors) and they change based on the notification as they are expected to. For me I have red for sms/mms, green for emails, blue for social network updates, white for woot, and yellow for default and they all work as expected. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Wow giant image fail. Was a picture of a log and a cat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glwilliams4:
When you say "some limitations with the mixing LEDs" could you give a few examples? Like is your yellow really yellow, or is it like half green, half orange? Is your white really white? I ask because I'm beginning to think maybe one of my LEDs is dead because the colors seem to be so off. I've tried using the ROM Control LED app, LED Tester, and Light Flow (with S3 Root checked) and my colors don't seem to be that accurate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electronics18:
That is exactly what I see, yellow is not going to be really yellow because there is no yellow LED it is mixing green and red, it is just mixing the the Red Green and Blue LEDs to make all the different colors with white being all the colors on full. This is a limitation of the hardware and I do not think there is any way to really ''fix" this. I have tested it on a couple of phones from different carriers and they all look the same, there is nothing wrong with your phone. Only thing you can do it play around with the colors to alter the intensity of each led to change the color as best you can. With the exception of Green Red and Blue, no colors is going to look completely accurate. I think the three LEDs are too spread apart inside the phone so you can see each color too easily when you try mixing them for the different colors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glwilliams4:
Thanks a lot man, that's what I wanted to hear. Wasn't sure how many LEDs were inside it to begin with so I wasn't sure what colors I should expect to be clear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Shoulda known.

Back to troubleshooting. Sigh. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Just use lightflow and you can test the colors while setting everything up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Not only do LED's work, you can select what color you want each notification to display.

It's built into the rom.

Missed call = blinking red

SMS = blinking purple

Email = blinking blue

etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rambo8987:
Where
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
ROM Control/LED
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] undisputedfb:
this works way better than liteflow
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fals3illusion:
Best ROM I have used on my gs3 so far. Keep up the great work !!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
ok. I had already played with that but thought I was missing something...because every time I picked a color on the

palette, the color the "test" showed was completely different.....And if I went too close to either end of the spectrum in the vertical color meter....I got no blink at all. That sound right or I need to wipe again?

When running this I did like a double wipe before installing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
All I can say is I have no issue using the built-in LED notification.

Of course there are limitations on the colors you can pick. Try to blend too much and you get white or something that you didn't really want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johentie:
Amazing Amazing work!! i was waiting a little to jump on a JB ROM.. and i took the plunge today... and i love it..

BUT.....

I am on Rogers and Do not get LTE.. that's a little but of a deal breaker for me.. i really wish i could stay on the ROM but after experiencing LTE i will have to wait to jump on this again!!

thanks for all your hard work devs! Keep it up and hopefully the LTE issue will be addressed when you guys have the chance and the time : > until then....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pussyliquor:
Look in FAQ's. Task doesn't need LTE for rogers and is tired of hearing about it. He'll add it when he adds it. Not trying to be rude but that has been heavily covered.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qnet:
I've been lurking on this thread for awhile. I just wanted to say I really like this Rom. I've been switching back and forth between this and the stock Rom and think I'll stick with this latest version for awhile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dondabomb5:
Best ROM for the S3 Hands down. Followed the instructions in the OP for the 8/20 and everything works GREAT. I am a supporter and will never flash another ROM. Glad to see you open the thread to Q&A as well because things were getting a tad ridiculous. Task you are the man and I truly appreciate you helping me in my switch from iPhone (5 years) to pure ANDROID. I have already donated but plan to do so again very soon. Your work is greatly appreciated by me. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaahinjjj:
same problem here. Do you happen to have a Canadian version of S3? Mine doesn't even work with light flow (even the new version). With this rom no matter what notification i get, my led always blinks white
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Nope. I'm at&t, US. Gonna give it another go tomorrow and report back. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
I have the same thing. I've learned I just have to "play" with the color pallet to get the color as close to the color I want. Sometimes it the hardware (I'm figuring) can't handle what I'm telling it to do it will display solid red no blink. Weird... some just work better than others I guess....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
So after flashing this build about 10 times I cannot figure out why my voice to text doesn't work properly. It will work properly at first and listen to all I have to say but eventually it will only listen to 3 words or so. I have tried redownloading ROM and GAPPS and wiping everything rebooting recovery and wiping again and flashing the ROM and without installing anything it worked at first. After letting it sit without installing anything it only listenings to 3 or so words I say. Something has to be causing this. I've never gotten a logcat before and I'm not even sure when I would need to grab one since I never know when it's going to stop working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Alright dude. After multiple reports without any useful information that would even begin to help me help you, you are basically beating a dead horse at this point. I would just try a different ROM or something if it is this important to you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nexii:
Guise, How do i screenshot again? i cant find the option anywhere. i feel so noobish...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
Volume down+power for a second
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darkbandit14:
Just got the ROM installed, very nice so far. Just one question and maybe it already has been posted, if so please forgive, but short of using Nova Launcher, is there a way to get Google now using the standard launcher? I have tried double tapping the home button and the setting button but nothing happens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Nah the regular launcher won't work for that because it doesn't have the option to remap that key to the search function which is Google now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Roco91:
You can turn on the Nav buttons in settings then just swipe up on the home button to get to it. I've been using the Nav buttons since they were put in and I'll never go back to using the physical keys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
my benchmark from your blazing fast setup. How's this compared to others?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Nobody really cares about benchmarks here. They're just random number generators.

Sent from my GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thejust:
Check out the gerrit from yesterday

http://gerrit.sudoservers.com/#/c/2805/

Oops quoted wrong post but lte anyway lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
I asked what I can do to help you figure this out. I could grab a logcat but it happens so randomly I wouldn't know when to grab one anyways. I thought I provided some useful information. The fact that it stops working after a fresh install after working for a while without installing any app strikes me as something that might be useful.

Besides no other ROM comes close to comparing to your ROMS. I could not imagine running anything else on my phone. I ran your AOKP on my gs2 forever and I plan to run this because it is the best. Just tell me what you need for me to help you help me and I'll do it.

EDIT: Just reflashed again this morning and it is currently working. When and if I notice it stops working again, what should I do to help you figure this out? Okay the voice to text was working fine I restored my apps, it still worked...but after I setup ROM control it stopped working. I changed my clock to center with small am/pm, set my battery to circleMOD, enabled weather, and enabled battery on lockscreen. Now my voice-to-text only will listen for like 3 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johentie:
i am aware.. i never asked him to add it for me..nor did i complain and said the rom isn't well done.. i said i will wait for it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unknownyello:
using trial and error, try changing those settings in ROM control back to default and see if that fixes the issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johentie:
so does this mean it can be added by someone(i don't mean this ROM, but AOKP ROMS in general)? they just need to pick up the code etc etc .. sorry i'm new to the AOKP