yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] pschatz12:
So if I just turn power saver on when running r64 then the cpu will max @ 1.3 & physical if power saver isn't enabled it will be 1.9 by default? I'm inexperienced also and leave power saver on bc over clocking scares me! Lol and help and knowledge would be greatly appreciated!
[Verizon Samsung Galaxy S III] Sccrluk9:
Correct. You can use System Tuner or SetCPU as mentioned earlier to lower the clock back down to 1.5 if you want though. In my experience power saver really didnt give me much more battery life so to me limiting the CPU wasnt worth it to me.
[Verizon Samsung Galaxy S III] MrBrady:
Curious about Synergy users' rooting methods - did you flash the Route66 pre-rooted ROM or did you go from stock and root manually?

EDIT: I'm consistently getting repeating Navigation instructions, no matter what ROM I run. Was curious if it was somehow related to the original rooted system or the actual Google Maps app (updated twice since first experienced the problem), since those are the only two consistant things.
[Verizon Samsung Galaxy S III] Sccrluk9:
I rooted from stock using this though all ways will leave you in the same boat.

http://xdaforums.com/showthread.php?t=1792342
[Verizon Samsung Galaxy S III] jcurley:
I wonder if ziggy can do a voodoo sound hack like on the Fascinate. That really boosted all around levels.

Sent from VZW S3 all Synergized up r64, OC to 1.21 GW
[Verizon Samsung Galaxy S III] taeksoo:
Thanks for that. I actually restored to earlier back and saw it still exists. So could be right. But I just deleted all folder under it but still have problems.

Any other suggestions? Thanks in advance.
[Verizon Samsung Galaxy S III] prdog1:
As a long time user of Ziggy's kernels working with Ziggy and Chingy since the T-bolt and running even unreleased kernels I would give Ech and Ziggy some time before jumping kernels. Rom changes as well as kernel changes can conflict and slow benchmarks. You have the privilege of having some of the best devs in the business working together to create the best experience possible on this device. Rule number one is let rom and kernel settle. My scores have gone up 1000 points on both Quadrant and Antutu in the last 24 hours since I moved from 1.7 to 64. I also always do full wipe on any flash. Full wipe, flash and data restore from Nandroid always trumps straight dirty flash where system bugs can still be transferred. I have not searched out all bugs yet as I prefer to let rom and kernel settle to fix itself if possible. I have not seen any data or wifi problems on 1.6/1.7 or 64. Battery has been awesome. Give the devs a break to learn and work out everything they can on this new device. It will pay for itself in the long run and especially in the upcoming conversion to JellyBean. Just my personal observation and 2 cents. Keep up the awesome work Team Synergy. It is appreciated. :cool:
[Verizon Samsung Galaxy S III] MrBrady:
+1
[Verizon Samsung Galaxy S III] prdog1:
Search the thread. The thread for 2 fixes are posted a day or two back. :cool:
[Verizon Samsung Galaxy S III] d1ez3:
Yeah, that's the issue, it's greyed out and not selectable. I guess I will go back to the previous build for now on swype, doubt it's an issue with this rom.
[Verizon Samsung Galaxy S III] pdinphx:
From the earlier post ...

1. boot recovery (CWM) > advanced > wipe cache

2. reboot phone > Root Explorer > delete /data/clipbord/*

3. reboot recovery again > advanced > fix permissions

4. reboot phone > enjoy
[Verizon Samsung Galaxy S III] germster:
Can't connect to wifi anyone else having issues
[Verizon Samsung Galaxy S III] Kreeker:
Unlock your bootloader...
[Verizon Samsung Galaxy S III] rzwiefel:
As far posts about lower quadrant/speed scores go,

Now I could quite possibly be 100% wrong so please correct me if I am. Though from what I noticed the large factor (that I haven't seen approached) is not (entirely/partially/a little?) Software/etc but HARDWARE.

As CPU's speed up and increase load they get hot, fast. (duh:p) (Done much cooling/overclocking work with computers). As its known hot is bad. So, when CPUs get hot they turn the fan higher. (And we obviously lack one of these ..) And sometimes that's not even enough, so it's forced to throttle the CPU down as it aproches its maximum temperature. And we've all noticed when our spacebar feels like a skillet sometimes after you flash/intensive phone usage/etc.

Look at the context you are running your quadrant/etc in. Like after you've been using your phone for while and getting that CPU nice and warmed up. As I ran multiple successive quadrant tests I noticed two things: 1. I had a positive correlation in LOWER scores. 2. My precioussss was getting HOT.

Moral of story, stuck in freezer for a (brief, don't worry) amount of time... and surprisingly enough, higher scores!

Since our CPU is sandwiched between a a screen, other parts, a plastic cover, and for most of us a case/etc. Now add in that sweet, sweet overclocking to the mix. Hence it could be that: faster = too hot = lower scores. It is possible we have reached(/coming near to) the limitations imposed physically that will be difficult (not impossible ;) ) to overcome without hardware modifications...

So I hope someone has been working on an aluminum back cover that doubles as heat sink and vent.... :D you can rev your engine past redline as long as you want.. but its gonna get hot and blow unless you got the radiators of a veyron... just some food for thought. :)

Cheers!

And and as always thanks for the fantastic work everyone.

Sent from my Blazing fast S III due to Synergy Nightlies ;)
[Verizon Samsung Galaxy S III] germster:
It's unlocked
[Verizon Samsung Galaxy S III] Brian Gove:
I know it sucks, but read thru the last few days of posts if you haven't already. It's been discussed a lot - dunno if there's been a fix found. I believe a full wipe/factory reset fixed it for one person. I could be wrong though, I haven't used my WiFi at all so I haven't payed too much attention. (my 4g even tho crappy is better than any WiFi connect I can get around here)

Thank you, this will gimme a chance to see if I like it better :)
[Verizon Samsung Galaxy S III] ka1z0ku:
Yeah I notice I get the best benchmarks after I have had my phone turned off for a few hours, then turn it back on and set gov to performance. Everyone will have different results due to hardware but I have been getting 5400 - 5600 in quadrant with r64 (posted a screenie a few pages back).
[Verizon Samsung Galaxy S III] ufjay5:
What is the stock min freq? I just set the max back to1.5. What is the best governor for battery life? Thanks.
[Verizon Samsung Galaxy S III] dan_joegibbsfan:
I set mine too min 384 max 1350 all the time and min 384 max 384 for screen off with SetCPU from XDA.

After I flashed r64 my Antutu went from 5500 range to 6500 (running fully overclocked). I started on r23 and noticed an incredible performance increase but r64 was another incredible improvement even staying underclocked.

I have dirty flashed them all and have only seen one app act up (XDA) so i cleared cache, data, uninstalled, & reinstalled and now have no problems.

Great work synergy team!
[Verizon Samsung Galaxy S III] Metfanant:
I agree about the benchmarks and scoring better when the phone is cool...and lower performance when hot...

And yes, I was running benchmarks back to back...but that doesn't change the fact that the instant I flashed back to r60 the scores went back up...I didn't let the phone cool down, and I continued to run them after flashing r60 to make sure it wasn't a fluke, and the scores stayed consistent

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] prdog1:
My previous post explains this. Kernel and/or rom changes can affect scores. That is why the rom and kernel developers on Synergy are working together. Stock kernel with rom changes can drop scores. Stock rom with kernel changes can also drop score. That is why it takes both devs working together to find the problem. When you keep changing kernels and rom builds they have no way to answer your problem. They have to take current rom build and current kernel build and figure out what to change. If you don't let kernel and rom settle you basically on your own. That is what they are doing and it does not help progress by going backward.
[Verizon Samsung Galaxy S III] slvfox:
When you go into settings/about phone, what is the kernel version are you running?
[Verizon Samsung Galaxy S III] pschatz12:
Unlock it again... Or lock it up then unlock it...I thought I was unlocked and went back in ez unlock and re-unlocked it because I couldn't connect to Wifi either and blue tooth was acting funny. It's worth a shot
[Verizon Samsung Galaxy S III] Metfanant:
Nope...not buying it as an excuse...

I was running Synergy with Ziggy Kernel when the scores hit the crapper on r64...tried different kernels...no change...scores still sucked...

Swapped to r60 scores jumped up and stay there no matter what kernel I run Ziggy, IMO, or KT747...

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] prdog1:
If all else fails use Adam Outler's original unlock. Works every time. ;):cool:
[Verizon Samsung Galaxy S III] Neverendingxsin:
If your phone runs perfectly fine, and its plenty quick, why do the quadrant scores even matter?
[Verizon Samsung Galaxy S III] Metfanant:
Actually I was not discussing Quadrant...but ALL benchmarking apps...smart bench, antutu, etc...

The reason it concerns me is that it shouldn't happen...yes I realize that benchmark scores do not necessarily translate to real world performance...the fact is if my phone is achieving a certain score consistently...and then all of a sudden is score 1000 points less...that is indicative of SOMETHING being off... no matter how hard people want to try and discredit benchmarks...

I'm not concerned with "you're phone scores 5000, why does mine only score 4800?"

I'm concerned with...my phone was scoring 3000 in a certain test...and is all of a sudden scoring 1800 in the same test...and clean installs can't fix it...

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] clambert11:
I don't care about scores but I do care about performance. Something was wonky with r64 for me too and battery life was fairly bad. Rolled back to r60 and things were fine again.

This is stuff you expect with nightlies. It doesn't bother me in the least as it's part of making the ROM more solid.
[Verizon Samsung Galaxy S III] Metfanant:
Don't get me wrong...I love the ROM its one of my favorite ROMs on any phone ive ever had...

I also expect things like this from nightlies..and I'm not concerned about it all that much...

I'm just not going to let people just dismiss my concerns as "irrelevant benchmark scores"

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] Neverendingxsin:
I've personally never ran any of these tests on my galaxy S3 and i've never noticed a dip in performance and i run the same cpu speeds and profiles every flash. I think what happens is people run these tests and assume something is flawed when the phone may be running perfectly fine.
[Verizon Samsung Galaxy S III] taeksoo:
Dude, I swear I read all the threads as I followed this from the beginning. I guess didn't pay too much attention to this because I didn't have this problem until now.

This DID solve my problem. Thanks allot for the instructions man! I'll try pay attention to what I read next time.
[Verizon Samsung Galaxy S III] rzwiefel:
As all things, I do believe there is two sides to the story (in this case, probably more). I'm sure its a combination (kernel,temp,ROM,etc) that contribute... but that's why the nightlies exist, so now we just need to collaborate and find all the culprits to help E and the team snag these baddies! Everyone pound their respective views on likely causes and we'll soon iron out all the wrinkles!

Cheers!

Sent from my Blazing fast S III due to Synergy Nightlies ;)
[Verizon Samsung Galaxy S III] prdog1:
Scores do not matter if it is smooth and fluid. But you cannot flash and run scores. They will be bad. :cool:
[Verizon Samsung Galaxy S III] Metfanant:
I would agree with you, but there is no reason for scores to plummet on the same device that's all

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies

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

I agree that scores don't matter in general...but if I've been achieving a certain score...and then all of a sudden the scores plummet and stay there...and the only way to fix it is to flash an old build something is up

If you can't flash and run scores..explain how flashing back to r60 immediately remidied the problem??

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] prdog1:
[/COLOR]

If you can't flash and run scores..explain how flashing back to r60 immediately remidied the problem??

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies[/QUOTE]

Because it can be rom or kernel. That is why you are lucky you have the rom dev and the kernel dev working together. If you would take the time to let both kernel and rom settle you would have seen the scores increase. If you nanded back you just went back to what was already settled. If you read my posts as a bonified tester for roms and kernels it explains how it works. You have to run a combo for anywhere from 24-36 hours before you get full performance. I flashed 64 yesterday from 1.7. My scores on both Quadrant and Antutu were 4000. After 24 hrs I'm at 5600. I rest my case. :cool:
[Verizon Samsung Galaxy S III] Karl:
can some please PM me a mirror i tried download more then 10 times everytime i get MD5 mismatch
[Verizon Samsung Galaxy S III] Neverendingxsin:
Personally i would just wait for tonight's nightly instead :)
[Verizon Samsung Galaxy S III] rzwiefel:
Matter not, scores do they? My padiwan have much to learn, do you. Try zipping your CWM directory and tell me if think faster is better ;) just playing though!

All jokes aside, constructive debate and problem solving is awesome for dev work! So let's not let our opinions and prides get in the way and just go pound bugs and get some concrete evidence of what's going awry so we can help E out! Go team go!

Cheers!

Sent from my Blazing fast S III due to Synergy Nightlies ;)
[Verizon Samsung Galaxy S III] Breezer23:
Looking forward to 66 and the new kernel!
[Verizon Samsung Galaxy S III] Karl:
alright.. i guess :crying:
[Verizon Samsung Galaxy S III] Metfanant:
Because it can be rom or kernel. That is why you are lucky you have the rom dev and the kernel dev working together. If you would take the time to let both kernel and rom settle you would have seen the scores increase. If you nanded back you just went back to what was already settled. If you read my posts as a bonified tester for roms and kernels it explains how it works. You have to run a combo for anywhere from 24-36 hours before you get full performance. I flashed 64 yesterday from 1.7. My scores on both Quadrant and Antutu were 4000. After 24 hrs I'm at 5600. I rest my case. :cool:[/QUOTE]

But your logic fails because I did NOT nandroid back to r60...clean flash with a complete wipe...let's go through the whole process...

1. ran r60 with both Ziggy and 747 kernel...never let any of them settle...scores were fine...

2 dirty flashed r64 with ziggy kernel when it came out...roughly 24 hours later (settle time) ran benchmarks...scores sucked...

3. Tried 747 kernel...no change...

4. Data wipe...no change...

5. Data wipe...reflash of r64...no change...

6. Data wipe flash 747 kernel...no change

7. Data wipe flash r60...instant change..no settling...

8. Flash 747 kernel to test...scores stay high...

Your theory simply doesn't hold any water in my case...

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] aypeeootrek:
Been on 55 for a few days now and everything has been perfect. Can't thank team synergy enough.
[Verizon Samsung Galaxy S III] prdog1:
Benchmark screenshots on release 64 after 36 hours. Full wipe with Modified Jelly Bomb. :cool:
[Verizon Samsung Galaxy S III] boynamedstacy:
Jesus, can we drop the benchmark concerns already!? If E thought this was a concern he would have jumped in by now and said something about it. In case you haven't noticed, he does read this thread and only comments on things he feels are relevant and/or important bugs. Since this conversation has been going on for multiple pages I would assume its safe to say he's not concerned nor considers this a bug. Welcome to the nightly life :)

If your phone is snappy... ENJOY IT! Dont compare it to what you ran two days ago. In two days it will be something different anyway...

/rant

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Metfanant:
so i implore you to explain why my scores were so significantly lower...and why the old build makes it better...whether E thinks its a bug or not doesnt particularly concern me...its not widespread...but i would like to see if i can track down WHY it happened on my phone...
[Verizon Samsung Galaxy S III] prdog1:
I agree. But the only way to teach them is to explain why and how it works. Then maybe they don't just flash and expect 7000 benches. The dev if he wanted could make them show 10,000. lol :cool:
[Verizon Samsung Galaxy S III] EM2_Rob:
Worked like a charm.
[Verizon Samsung Galaxy S III] Metfanant:
youre not teaching me anything...because you're all knowing explanation makes no sense when applied to my situation...if "settling" made such a huge difference...then why would the install that had "settled" be the one with the low scores??
[Verizon Samsung Galaxy S III] prdog1:
Apparently you did not read all the posts that explain why changes in kernel and/or rom affect the score. Like the other poster said if it is smooth and fluid scores are irrelevant. There is no problem in the latest 64 version and the current Ziggy kernel as you can see from my posted scores. I have seen lesser scores from the first unsecured kernels on stock rom. Even stock kernels dropped the score on stock roms.
[Verizon Samsung Galaxy S III] Metfanant:
ive read and understand everything PERFECTLY...you're logic would suggest that a clean install of r64 with the Ziggy kernel should have cured the issue...it did not...

i can swap kernels every couple minutes on r60 (i tried 3 different kernels back, to back, to back and back again just flashing and running benchmarks over and over again) and have NO negative impact on scores...yet the normal flash of r64 with the "correct" kernel (ziggy) caused low scores AFTER the all important settling...and no number of wipes/kernel swapping would change it...

SOMETHING in r64 was not playing well with my CPU...period...whether it jives with your "theory" is irrelevant...

Edit: Regardless im looking forward to flashing r66 tonight and hoping it clears up any issues
[Verizon Samsung Galaxy S III] prdog1:
I'm done with this. R64 plays fine with my CPU. If you are flashing multiple kernels and backing up you are not helping the devs. My scores are fine after the move from 1.7 to R64 seeing how this is only basically Beta 2 of Ziggy's kernel. Mods you are welcome to delete these posts as they seem to be irrelevant. :cool:
[Verizon Samsung Galaxy S III] Metfanant:
wait, so because there is an issue on my phone, but not yours it should be ignored??...yeah, that makes sense

honest question...can you not read? or do you choose to ignore posts because they don't agree with your opinion??...

1. the problem first occurred on r64 with the ZIGGY kernel...no kernel flashing...flashed r64...made no changes for about 24hrs...

2. i flashed the other kernels in an attempt to fix it (because 747 ran PERFECTLY on previous builds)

3. multiple fresh installs of r64 with Ziggy kernel did NOTHING to fix the problem

4. i did not use ANY backups during this process...all clean installs, with data/cache/dalvik wipes using regular synergy .zip files NOT nandroids...

so again i ask the question...because your phone is working fine...it means that anyone having problems is doing something wrong and there is nothing wrong?...please...
[Verizon Samsung Galaxy S III] trbman:
has the volume hack been removed? I wanna update but not until it's gone. It messed up a few sound levels on some of my apps

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] Metfanant:
E said it was coming out...and i THINK i also remember him saying its tied to the kernel...so since Ziggy's kernel is what is being updated tonight its possible...but im not sure
[Verizon Samsung Galaxy S III] slvfox:
Let's see now. Two pages at 40 posts per page and you are the only one complaining about scores that don't matter and want to argue with everyone. I think it's time to flash another ROM that will give you the worthless scores your looking for.:good:
[Verizon Samsung Galaxy S III] Breezer23:
Hahaha. People and their benchmark scores.

ANYWAY. How about you flash one of the other three kernels and stop with the benchmarks.
[Verizon Samsung Galaxy S III] prdog1:
What I am telling you is if doing nightlies the scores will change nightly. All devices are not the same. My scores were worse than stock but I don't expect them to be better each time cause changes in rom and/or changes in kernel can cause the same effect. Devs can not go by previous or other kernels or older builds. They can look at older builds of rom and run the diff and see if there is bad code. The kernels are new and take a while to beat the code. If it was easy you would be running 10,000 on stock kernel but would not have the tweaks that the kernel developers are able to give you that the manufacturers couldn't. These are not Samsung S3 devs. They have spent years on other devices and kernels. They are learning like us but I think they are doing a great job learning this device and Samsung code so that they can hopefully move to JellyBean with a knowledge of what Samsung is doing without them or us starting from scratch.
[Verizon Samsung Galaxy S III] Metfanant:
holy crap!...

1. im not arguing...trying to figure out why my CPU is not performing as well...period...but not going to sit back and be attacked as doing something "wrong" when im not...

2. thats the point...Synergy WAS performing right...and IS performing right on other phones...but something was wrong on mine and nothing but a flash back to r60 could fix it...that is NOT right...whether you want to believe it or not...there is no reason for my CPU related scores to be 1000+ points lower on a particular benchmark running r64 when compared to r60...
[Verizon Samsung Galaxy S III] drbveb88:
Hey everyone. Took a break from synergy but may wanna come back, what is the most stable build out of the recent nightlies. Looking for good and stable data. While cm10/paranoid are really sweet, my data drops are killing me.

I tried reading up a little but all I can find is posts relating to benchmark scores.

Thanks for the opinions.

Shhh.. my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] Metfanant:
the builds don't really change from build to build as far as stability is concerned...its not like a AOSP rom in that sense...i would just go with the nightly that comes out tonight in a few minutes r66
[Verizon Samsung Galaxy S III] trbman:
the benchmark argument is preventing people from getting the most out of this thread. needs to be cleaned up a bit.

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] epagib:
r66 just went online!