yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jcurley:
try a different command. Say contact Deborah. Play with it a little. It you just say a name the phone doesn't know you mean contacts or web.

Sent from VZW S3 all Synergized up r39, OC to 1.21 GW
[Verizon Samsung Galaxy S III] epagib:
Based on my personal experience:

Ran 1.7 for about 2 weeks. No fc, everything works.

Ran r56 for about a week. No problems either.

Has been running r64 since its release. Perfect to date. Have not had WiFi or 4g issues that's been mentioned, and phone runs cool on lagfree.

If you're going to take a plunge, I'd recommend r64 first. Any problems, only then I'd consider stepping back to r56.

- make sure bootloader is unlocked.

- full wipe

......there has been way too many improvements since, to start with 1.7. Plus 1.7 is not going back up your efs/meid.

---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

From a full charge last night = 8 hr 15 min on battery. 50 min screen time with 82% battery left.

Phone has been cool to touch. Lag free governor

Dirty install from r60
[Verizon Samsung Galaxy S III] pschatz12:
If media is eating battery just force close it and reboot your phone a couple times... It happened to me earlier and a couple times before this on earlier builds... A couple reboots solves it I think... I'm guessing it's a touch wiz problem and not synergy
[Verizon Samsung Galaxy S III] jlokos:
I flashed r64 over r60 and I'm using imo's .5 kernel. No issues and battery life so far is fine.
[Verizon Samsung Galaxy S III] pschatz12:
You have a download link for imos?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
0.6 was just released http://bit.ly/QFIVIS
[Verizon Samsung Galaxy S III] pschatz12:
Link didn't work for me?
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Try this then http://rootzwiki.com/topic/31329-kerneltouchwiz-leankernel-minimalistic-kernel-830-v06/

---------- Post added at 04:12 PM ---------- Previous post was at 04:04 PM ----------

Does anyone know of a flashable zip script that wipes all data, cache, etc and does a full clean. I came from my Galaxy Nexus and i used to use superwipe and it made my job a lot easier when flashing roms rather than doing it manually.
[Verizon Samsung Galaxy S III] redbearde:
Dirty flashed from 1.6 to r39 a little while ago. Today I dirty flashed again to r64.

Not a single bug. Working flawlessly. GPS locks instantly. Eschelon, you guys do incredible work.

Thank you.
[Verizon Samsung Galaxy S III] pschatz12:
Link worked... I sent you a PM... Hopefully you can give some insight! Thanks
[Verizon Samsung Galaxy S III] Glasairmell:
What was interesting for me was that Ziggy's Kernel gave me a better AnTuTu benchmark then the Imo v.06.
[Verizon Samsung Galaxy S III] Srambo217:
Is it normal to have so-so battery life the first day or so of flashing?
[Verizon Samsung Galaxy S III] redbearde:
I don't know what you mean by so-so battery life, but you might want to give it a few days to a week to get into a rhythm to see what it actually does.
[Verizon Samsung Galaxy S III] wmaudio:
Ok here's what's happening:

Restore r55 in recovery = normal boot, everything's fine.

Dirty flash from r55 to r64 using ROM kernel = hang at SGSIII white logo. Battery pull required to get out of it.

Clean flash from r55 to r64 using ROM kernel = hang at SGSIII white logo. Battery pull required to get out of it.

IMO .5 with both r64 scenarios = boots to SGSIII white logo, hangs for 20 seconds, then reboots to recovery and waits for action from me.

IMO .5 on r55 = normal boot, everything's fine, battery life so-so. No CPU control involved.

Someone had suggested I got a bad download even though the MD5 matched, so I am re-downloading again as we speak and will try to wipe all data/cache/dalvik, flash the ROM and try to boot. If that doesn't work, I'll battery pull and flash IMO .6 and try to boot. I'll report back when more info is available. Thanks for the great ROM E. I'll be donating tomorrow (payday!).

--edit--

Correction...I'm going to flash IMO .6 now while on r55 to verify it's working and therefore not the kernel.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Alright im all for removing the volume hack, turns out its anything that is over the internet that has a problem. Volume is messed up on skype, oovoo, google voice, so you can sign me up for removing the volume hack.

If anybody wants to test download skype from the market and do the echo test call and you'll be able to tell that volume is extremely low.
[Verizon Samsung Galaxy S III] supercell2000:
Is the Bluetooth connection issue fixed?
[Verizon Samsung Galaxy S III] Glasairmell:
I am going to have to second this.
[Verizon Samsung Galaxy S III] x86cpu:
It was fixed for me. Somewhere around r55. Mine wouldn't auto-reconnect and it does now.
[Verizon Samsung Galaxy S III] wmaudio:
Trying to download r64, very slow. It took 5 minutes to download 10MB.

--edit--

Spoke too soon. Stopped it and tried again, getting almost 3MB/s now.
[Verizon Samsung Galaxy S III] clambert11:
Anyone having issues with QuickPic and the last couple releases? It doesn't see the sd card right away and literally takes forever to scan for new pictures on the sd card. Maybe something changed with QuickPic but it seems fine on my wife's stock GS3.

I tried uninstalling and re-installing to no avail.
[Verizon Samsung Galaxy S III] M_T_M:
I'd say corrupted SD card about to croak..might want to back it up if haven't lately :(

Went through almost same issue and some day..bam! Everything was gone :eek:

I was the first to become second at being first.....PROBLEM??
[Verizon Samsung Galaxy S III] Karl:
did you get it fixed?

page 666 :good:
[Verizon Samsung Galaxy S III] jcurley:
Mine has the same problem. I have been using the stock gallery without one issue. I read that quickpics last couple of updates have been to address a problem with the sd card not showing up. I think it is an app issue not a rom issue. Had the same problem on beans10.

Sent from VZW S3 all Synergized up r64, OC to 1.21 GW
[Verizon Samsung Galaxy S III] wmaudio:
Got wife aggro, I'll be flashing it in about 45 minutes or so and will report back. Thanks for the help. :)
[Verizon Samsung Galaxy S III] s197:
QuickPick is working fine of r50 so I don't think it's the app.
[Verizon Samsung Galaxy S III] Srambo217:
As in 'worse than stock'.
[Verizon Samsung Galaxy S III] doeboy711:
Sometimes you can have not the best battery life the first time you flash, but everyone's phone is different and will react a lil differently.
[Verizon Samsung Galaxy S III] Brian Gove:
I've had no issues with QuickPic and I'm on r64, r60 before that.
[Verizon Samsung Galaxy S III] Excessiveidling:
On r64 with synergy kernel and noticed haptic feedback doesn't work as it should. If I select something on the screen it doesn't vibrate like it did default or with clean rom... It does vibrate in other apps like my keyboarf(swiftkey) but that's the apps setting I figure.... Any ideas? I otherwise no issues that I've seen so far
[Verizon Samsung Galaxy S III] guthrien:
I had back and forth issues with QuickPic on stock recently. I think there's something wrong with how it builds a cache sometimes.

Does everyone who reports battery problems run BetterBatteryStats or the like? It's really hard to subjectively judge what's eating battery life when we have different apps installed. I'm getting really good battery life but I measure what's happening with BBS.
[Verizon Samsung Galaxy S III] pschatz12:
Do you have power saver mode on? And check your settings after because if you switched it on then off it doesn't turn haptic back on
[Verizon Samsung Galaxy S III] Excessiveidling:
No power save mode is NOT on... Never turned it on and nor will I :) have rebooted as well warm and powered off for a minute or two them back on.... Flashed using cwm 6.0.1 not touch and previous rom was cm10 kang invisiblek
[Verizon Samsung Galaxy S III] kenmills78:
Off topic a bit. How does quick pic make money?
[Verizon Samsung Galaxy S III] itzwolf:
Just had another hiccup of wifi on r64. Had to disable and then re enable wifi to get it back. It's as if I'm connected but lost dns so doesn't know what to do. I cannot ping the phone either when this happens.

Edit:

I was cruising along using wifi when it happened so it was a sudden thing. I did notice my battery had just hit 30% also.
[Verizon Samsung Galaxy S III] andreiantal:
Yes I tried Skype and it's so low it is unusable.
[Verizon Samsung Galaxy S III] itzwolf:
I say make the volume hack an add on instead and go back to the stock setup.
[Verizon Samsung Galaxy S III] Neverendingxsin:
I asked about that and E said it's in the kernel and would be really hard to do.
[Verizon Samsung Galaxy S III] chocolate8175:
I reported 4g issues for like 3 days and nobody seemed to care or share the same problem I guess, since r64 I haven't had the problem though. So I don't know whats up with that
[Verizon Samsung Galaxy S III] chetqwerty:
same here issues exactly as you described. noticed it with the nightlie builds. Speaking of quickpic, anything anyone can do about a hack for the messaging database to allow quickpic to read it? getting load failed error when trying to view a mms picture directly from the messiging app or verizons messaging app. has to be a database permission because it happens in both of them. actually if someone can point me to the database file i can try changing the permissions myself. sorry to hijack a bit but then again fixing stupid manufacturers errors is what rom building is all about.
[Verizon Samsung Galaxy S III] Old MuckenMire:
Another vote here for dropping the volume hack
[Verizon Samsung Galaxy S III] Glasairmell:
I keep getting com.google.process.gaps has stopped message.

Wonder if I have to do a clean install. Did not start coming up untill R55.

Regards!
[Verizon Samsung Galaxy S III] Neverendingxsin:
I would do that :)
[Verizon Samsung Galaxy S III] d1ez3:
please ignore
[Verizon Samsung Galaxy S III] beastmods:
Would like to see awesome beats equalizer (beats by dre).

had it on my sprint gs3 and it was very nice. Freegs3 ROM in sprint forum.
[Verizon Samsung Galaxy S III] mbonamassa:
Thanks for all the suggestions on fixing the WiFi. Unfortunately nothing has worked. I still can't toggle WiFi on or get tethering to work. It is as if the WiFi device is off. I tried turning off the power save, reflashing. I think I did a full wipe but not sure. I wiped system cache and dalvik and flashed. Using r64.

Any other ideas?
[Verizon Samsung Galaxy S III] silver04v:
Is your bootloader Def unlocked? When flashing the rom what does it say about the kernel flashing?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] Metfanant:
something between r60 and r64 absolutely KILLED my benchmark scores...particularly CPU related tasks...and its most noticeable in SmartBench 2012...my productivity score is ~800-1000 points lower on r64 when compared to r60....i tried all the possible wipes, re flashing, tried different kernels, and everything else...but as soon as i went back to r60...my scores were back to normal...

i know benchmark scores need to be taken with a grain of salt...and i dont use them to compare devices...but something is weird when my phones scores drop that significantly...and flashing a previous release of the ROM brings the scores right back

in the first image below you can see my scores prior to 8/30 being what ive come to expect from the phone since having it...then you can see my 8/30-8/31 scores dip DRASTICALLY...then in the second pic you can see that the scores went back up after re-flashing r60...

any ideas?
[Verizon Samsung Galaxy S III] prenedo:
Need to wipe data/system and dalvik for a full wipe. You'll know when you do a full wipe. Your phone will be reset.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Leave the volume hack in. Does anyone know why wifi tether usually needs to be turned on and off several times before it e will work and show the ssid?
[Verizon Samsung Galaxy S III] sherdog16:
Just want to weigh in on the volume hack. If it's borking things for people lose it. If you want stuff louder just install volume+. Boom, everyone's happy :)

Love the rom E and team, thanks.
[Verizon Samsung Galaxy S III] GREGHARKINS:
+1
[Verizon Samsung Galaxy S III] jbeitel:
ok, what recovery is newer than 6021 cwm? I don't want twrp because it doesnt work with vrthemes.
[Verizon Samsung Galaxy S III] ka1z0ku:
Build r64 is the best yet, may stick with it until next big set of changes (unless I find a bug I can't live with).
[Verizon Samsung Galaxy S III] Kreeker:
I noticed this as well last night, and I don't have any ideas :(

My quadrant is 4715 on r64, but was between 5100-5200 on r60.

The phone is also noticeably sluggish.
[Verizon Samsung Galaxy S III] redbearde:
In Wifi Tether

Settings > Change Device Profile

Change it from Generic ICS to Samsung Galaxy Nexus (CDMA/LTE)

I've read different people say they've had better luck with one or the other, so don't feel married to either setting.
[Verizon Samsung Galaxy S III] Metfanant:
right...in quadrant my scores were a few hundred points lower than normal...Quadrant is so all over the place though...so thats why i tried running some stuff in SmartBench and Antutu as well...and it was the same thing...anything GAMING or GRAPHICS related seems to be ok (as you can see from my "gaming scores" in the smart bench history screenshots i posted not falling off that much....but anything that was more CPU calculations just plain sucked...

i wiped and wiped, and re-flashed r64 multiple times and was getting the same scores....i flash r60 and on the first boot i score 800-1000 points better in productivity on SmartBench...and its stayed right there ever since flashing back...

even if there are no commits to the build bot today, ill try flashing whatever gets spit out tonight and see how things go...
[Verizon Samsung Galaxy S III] wmaudio:
Sorry about the late response. Yes, I'm fixed. I re-downloaded r64 and flashed it and everything is working now.

However, ever since r55, I've been having an issue with restoring data using TB. App restores work fine, but the issue lies in restoring SMS via XML files created using TB as well as DB backups using the scheduled backup functions in TB.

When I try to restore using the XML and TB, I got my text messages back but all call log entries and all contacts are deleted. My contacts are all in my Google account and only display contacts from my Google account on the phone, so I was worried that it had wiped out my contacts in my Google account too, but when I log into my Google account all of my contacts are there. I delete my Google account from the phone and re-add it and the contacts still don't come back down even though the Sync settings are set to do so. The only way I can fix it is to restore from backup.

This functionality has worked for me since 1.4, and I do it almost daily as I receive a lot of calls and messages that I need to keep. However, as of r55, this issue has existed. I like using TB to do the SMS/MMS backups because it saves everything, including MMS, and once it's set up it's basically a one-click process.
[Verizon Samsung Galaxy S III] astrocity:
I would also like to advocate the removal of the volume hack. As a previous GNEX user I'm familiar with Volume+. Any type of voice chat or google voice message playback as we know cuts off unless you turn the volume down.

I read that this was linked somewhere in the Kernel so Esch said it was a tough removal. Does anyone know of a Kernel that works that doesn't include this in and works well with synergy? I've read alot of conflicting information surrounding IMO's kernel and used to be a franco guy.
[Verizon Samsung Galaxy S III] wmaudio:
Have you tried r64 with different kernels?
[Verizon Samsung Galaxy S III] boynamedstacy:
No issues with IMO here. V6 dropped yesterday and has been working great. I'd give that a spin so you can draw your own conclusion :)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Metfanant:
tried it with the stock (Ziggy) kernel...as well as the KT747 kernel which ive run just fine for weeks now...in the screenshot where it shows im overclocked to 2.1ghz its running the KT747 kernel on r60...
[Verizon Samsung Galaxy S III] gfausey211:
That's would be awesome
[Verizon Samsung Galaxy S III] Kreeker:
I tried IMO's kernel, and I'm still getting the lower quadrant scores.

Of course benchmarks don't mean jack, but it's worth noting.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Is there a way to remove the "Select Input Method" notification whenever I type?
[Verizon Samsung Galaxy S III] Nnyan:
It should give you the option to save that choice once you make your selection, is it not?
[Verizon Samsung Galaxy S III] djd338:
I've been using TWERP for several days and it's working great and a pleasure to use. The recovery has recently been updated to 2.2.2 and has fixed some sgs3 problems (do NOT use 2.2.1). The Goo app has also been updated to reflect the newest recovery. Here's a quote from Dees-Troy about vrthemes:

Most of the time if a vrtheme doesn't install it's because of the dynamically linked zipalign binary that's being used. If you simply replace the dynamically linked zipalign binary with the static binary linked below, it will work just fine.

http://techerrata.com/file/twrp2/utilities/zipalign
[Verizon Samsung Galaxy S III] Jurassitol:
I've been dirty flashing every nightly, currently running yesterday's build and I see no real issue with quadrant scores (5616).
[Verizon Samsung Galaxy S III] pimpmaneaton:
Yeah as stated just above twrp is working with vrtheme. Just flashed my installer with the newest twrp 2.2.2.1 last night and all went through just fine. All of my aroma options worked flawlessly.

Launched from Hot Rod running Synergy!!
[Verizon Samsung Galaxy S III] Kreeker:
Hmm that score does look very good.

What kernel?

What OC are you at? What governor? What are you using to change oc/governor?
[Verizon Samsung Galaxy S III] Jurassitol:
(Synergy Stock) Ziggy kernel, on-demand/cfq through SetCPU.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Uncheck all the other keyboards in settings except the one you want to use
[Verizon Samsung Galaxy S III] jcurley:
I am getting 5200-5300 at 1.7 clock with Voltage control.
[Verizon Samsung Galaxy S III] pschatz12:
Anyone have issues with call quality? Sounds a little choppy when the person on the other line is speaking. On latest build with the kernel that comes with synergy.
[Verizon Samsung Galaxy S III] goldsmitht:
i've got the same issue, and when i go in to settings i can't uncheck them.
[Verizon Samsung Galaxy S III] mbonamassa:
Yes it is unlocked. I used ez unlock and when I go into that it shows unlocked. No errors flashing but I am nother sure what specifically you are asking about a message during flashing

---------- Post added at 06:35 PM ---------- Previous post was at 06:29 PM ----------

Ahhh so if I do a full wipe all ter data is gone - makes sense. I am guessing that the contents of sdcard (not the the external sdcard) will be gone too? If so, then I need to read posts on hit to get twrp to see my ext sdcard to load roms. Any thread pointers are welcome.

Btw: been away from this stuff for a while but it us great to see this community is as helpful and informed as ever!!!
[Verizon Samsung Galaxy S III] Excessiveidling:
Noticed something strange that might just be the software I use buuuuut... Running r64 and notice every now and then the touch sounds for everything (aka the water drop sound) that I have turned off turns on randomly and I have to re select it... Strange
[Verizon Samsung Galaxy S III] taeksoo:
I'm on r64 and the third g is super fast and great. Only thing I noticed is the Copy &Paste won't work properly. Anyone else having this issue?

It'll copy but won't paste or it'll crash the app when copying.
[Verizon Samsung Galaxy S III] sherdog16:
From my experience so far it's from using the camera...

I'm running r64 and the on screen keys mod
[Verizon Samsung Galaxy S III] eschelon:
Volume hack is coming out. Those that want the same functionality will have to use an app from the play store. Sorry to those that want it (including myself), but it's a luxury for you while it's actually breaking stuff for others. In that situation the choice is obvious.

Also, been testing some kernels all morning (took the day off as I had a wicked fever last night) and Ziggy has fully implemented the smartassv2 governor. My guess is he'll be committing it later today assuming all goes well. Also, lagfree (Ziggy's favorite) will now be the default instead of ondemand.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Good to hear Eschelon :) I actually really enjoy the volume hack you implemented, and would rather not use a market app, but since its breaking a few things that i use (especially skype) ill just have to tough it out. Its good to know that you listen to what people's wants and needs are and don't mind helping us all out :)
[Verizon Samsung Galaxy S III] blestsol:
*Le sigh *

Show must go on though.
[Verizon Samsung Galaxy S III] germster:
I'm on r64 noticed Screenshot UX not working correctly. Everything else is awesome fast.
[Verizon Samsung Galaxy S III] Ignite023:
Where do I set the governors? Can't seem to find the settings :\
[Verizon Samsung Galaxy S III] Kreeker:
You have to use an app like System Tuner or SetCpu
[Verizon Samsung Galaxy S III] Ignite023:
Ok, thanks.. Coming from the Gnex and codename, the settings were part of the ROM.
[Verizon Samsung Galaxy S III] EM2_Rob:
I can't uncheck two of them.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Use titanium backup to either uninstall or freeze them, there probably system apps.
[Verizon Samsung Galaxy S III] RCOVA:
If you don't think you will ever use them then just delete them.

Edit: Damn ninjas.. Lol
[Verizon Samsung Galaxy S III] pdinphx:
All cut&paste items get saved in /data/clipboard, which never gets scrubbed. Once it fills to capacity (?), you start getting fc's and error msgs.

Use a file manager to manually delete the files or Tasker to automate the process.
[Verizon Samsung Galaxy S III] Brian Gove:
Is using the CPU options in ROM toolbox just as functional? Being the cheap prick I am I'd rather not buy another app if I don't have too lol
[Verizon Samsung Galaxy S III] astrocity:
Esch - Thank you for listening to your userbase on the volume hack. I'm sure I'll be complaining next that I can't find a good balance with volume+ or I won't be able to make it work or who knows what, but functionality seems to always be #1 for you, and that's why so many stick with you.

Cannot wait to try the new gov. settings and hopefully it won't be 1.9 out of the box. People inexperienced with cpu adjustments like myself will be thankful for this.

Donation is incoming. I will create a new post with the information.

Feel better dude, just know you've got tons of people out here loving what you do!

-Daniel
[Verizon Samsung Galaxy S III] mapatton82:
System Tuner has worked for me and it is free, you don't need the Pro version.
[Verizon Samsung Galaxy S III] Mystikalrush:
Im guessing this new kernal is based on Ziggys latest?
[Verizon Samsung Galaxy S III] samscinate:
Presents in Ziggys kernel.... this team is amazing. All the hard work is so appreciates. Makes this phone so worth it. Thanks guys!!
[Verizon Samsung Galaxy S III] eschelon:
The pro version of SetCPU is free for XDA users from the developer here: http://xdaforums.com/showthread.php?t=505419

That thread is a little outdated, but free is free :)

It will still be 1.9 by default. Zig is aware of the issue and has been working on a fix. It won't be included in tonight's newer kernel, but he is working to solve the issue. For now you'll still have to manually set it to 1.5 if you want, but rest assured we do intend on getting this remedied.
[Verizon Samsung Galaxy S III] d1ez3:
Anyone get the update to swype and no longer have vibrate on keypress?
[Verizon Samsung Galaxy S III] Sccrluk9:
Push and hold swype icon to go to settings and check vibrate on keypress.