yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Metfanant:
its not really a kexec thing...it happens on CWM 6.0.1.2 as well...which is the latest CWM...

im not sure im following you...

but ive never had a phone run better on ANY ROM than r60...and my phone has gotten progressively worse since then...my first EVER random reboot with this phone was on r68...and now today ive experienced lag in places ive never noticed it before...and had the phone become COMPLETELY unresponsive three times running 68 the first time...then updating to 71 and having it happen twice since...
[Verizon Samsung Galaxy S III] prdog1:
Been using them so long I can't even tell you. lol I use TIBU to backup app=data, freeze apps and delete those I can't any other way. My Backup is used for Homescreen replacement, contacts, sms, calender, phone logs, ect. I use both of these when nandroid data restore will not work. Nandroid data restore depends on the same rom build base and other variables. When it works it trumps all backup apps. I don't do nightlies every night unless there is a major reason too. I do test all Ziggy's kernels as I have tested and worked with him through 3rd parties since the Tbolt days. Ziggy is one of the best if not the best kernel developers out there. I am still on revision 64 after clean install from 1.7 and running Sept 1st kernel with both cores working. Overclock at 1.7 sticking after reboot with SetCpu is hit and miss and looks more like how soon clocking app gets root permission. Other apps getting root first seems to time out boot window for kernel. I am still testing but these are my observations. Even though I am still on revision 64 I have seen zero reboots. Will update to latest build and stick with latest kernel to try and peg the reboot problem down but I also refuse to dirty flash. :cool:
[Verizon Samsung Galaxy S III] eschelon:
Don't worry about rXXX

I stated a while back in the thread that our ROM files always say rXXX and then our buildbox has a script that checks to see which revision we are on and automatically changes to whatever "r" it's supposed to be so that we don't have to change it manually every day.

But last night the buildbox was having issues (how many of you noticed r70 was built and uploaded like 6 times before I fixed it :P ) so I had to make a build manually. Sometimes when I make a build I will manually change this rXXX myself to whatever it's supposed to be. But last night I was in a rush and very tired and I just didn't do it as I wanted to ensure you guys had a working ROM before I went to bed.

If it ever says rXXX it's fine, it just means that I had to make the build manually and didn't get a chance to change it. Nothing is broken.
[Verizon Samsung Galaxy S III] prdog1:
I only use Clockwork (Touch) on Tbolt . It was non compatible on Rezound so used Amon from the Father of all recoveries and still wipe x3 per his instructions. TWRP took a break when lead dev left the Team. CWM was it when we needed kelexc. I use TWRP now. It is awesome, works perfectly and only thing it doesn't do is Villian theme which works also if right zipalign is used.
[Verizon Samsung Galaxy S III] Metfanant:
ive always used CWM...just comfortable with it i guess...i was just trying to point out that its a generic "warning" of sorts in CWM...not a Synergy or kexec thing...people seem to think its some sort of glitch...its not
[Verizon Samsung Galaxy S III] prdog1:
I agree and good chance it will not be removed or fixed. For me TWRP is to easy to wipe even multiple times, Renaming with built in keyboard rocks and flash always works. lol If I need CWM to do something it won't do (such as Villian theme zip which is the only thing it won't do for now) there is no problem flashing recoveries back and forth. I came from Tbolt/Rezound. This **** is easy. :laugh::cool:
[Verizon Samsung Galaxy S III] s197:
Good idea, thanks. I tested using this method and it does look like the CPU comes on very briefly.
[Verizon Samsung Galaxy S III] Stryker1297:
any tips for getting rid of on screen buttons? search helped with nothing... liiked buttons for awhile but they are annoying at this rate:( great rom though! looks nice with real icon theme!
[Verizon Samsung Galaxy S III] Schaweet:
Yeah Reflash the rom. Just wipe dalvik and flash the rom again. They will be gone.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] prdog1:
They were added with zip by you. Only way to get rid of them is to reflash or restore nandroid unless Ech builds another zip.
[Verizon Samsung Galaxy S III] Stryker1297:
ahhh. was hoping it wouldnt come to that but ok thanks guys.
[Verizon Samsung Galaxy S III] Farabomb:
Coming from the charge this nightly thing is a little new to me. I'm running 1.7/clean1.0 now and I have tried others like cleanROM but I was having issues and never really got it looking how I like it on 1.7. Is it worth it to try a newer nightly revision and is a full wipe necessary? I can deal with the occasional notification issue I get but I'd rather not have to start from scratch unless it's that much of an improvement.
[Verizon Samsung Galaxy S III] prdog1:
Read and learn. There is no such thing as having to start from scratch if you read and learn the tricks. I can do a full wipe and be back with full theme in 30 minutes or less. lol
[Verizon Samsung Galaxy S III] JeepSRT8:
Anyone besides me having issues get an exact lock on r71? GPS is off by a few blocks..coming from a fresh install with everything wiped!
[Verizon Samsung Galaxy S III] Glasairmell:
What does GPS Test say?

What app are you using that says you are off by a few blocks?

Regards!
[Verizon Samsung Galaxy S III] JeepSRT8:
Downloading that app now..thanks. I just opened google maps and it kept jumping from location to location. Left it for 10 mins but it still couldn't locate me.

---------- Post added at 12:43 AM ---------- Previous post was at 12:34 AM ----------

Here is what i got from that app.

22 in view, 0 in use.
[Verizon Samsung Galaxy S III] Glasairmell:
Are you in doors? Zero in use is bad of course. Try a reboot.
[Verizon Samsung Galaxy S III] itzwolf:
My 2nd cpu core kicks on and off as needed. Been using lagfree on r68, great battery, and no issues whatsoever to note. Been dirty flashing but clearing cache and davlik cache since v1.6 which was originally a clean flash about four hours after getting my phone brand new.

I'm weary to jump to r71 since the phone has been amazing since I flashed r68.

Oh and no reboots either since moving to r68.
[Verizon Samsung Galaxy S III] evolishesh:
This might be stupid question, but my backup and restore is not workingk. It says that there's no back up account or restore account. It's not a big deal. It's that I'm so used to not entering my wifi password, or downloading my apps manually.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Any info/logs we should submit for the random reboot issue?
[Verizon Samsung Galaxy S III] Mystikalrush:
First time longevity test, on r66.

http://i49.photobucket.com/albums/f265/Mystikalrush/Screenshot_2012-09-05-19-15-48.png
[Verizon Samsung Galaxy S III] prdog1:
Did you turn on GPS. Mine showed 20 in view 0 in use till I turned on GPS and then showed 9 in use.
[Verizon Samsung Galaxy S III] d1ez3:
I went from 66 to 71 with a full wipe (was on imo's 0.7) but now all stock. After restarting I looked at the cpu in system tuner, and putting it on ondemand made the cpu settings basically go crazy. The 2 bars to set the speeds kept moving on their own regardless of what I chose, my phone got really hot (52 C) so it's in the freezer now. I will restart a few more times to see if I can choose my own settings. Did anyone else see this happen?

edit: seems to have normalized by itself now. I should always let phones sit for a while after new kernels/roms and restoring apps, this behavior is to be expected.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Always bag your phone (with rice if possible) before freezing it to avoid condensation build up. :p
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
This is incorrect. This seems to be a Synergy thing to me. Just to crack flash, I flashed Beans ROM and CleanROM and it doesn't show up. It only shows up when I flash Synergy.
[Verizon Samsung Galaxy S III] Coderedpl:
Does Synergy have themed google voice included or something? Or is it the rom itself? It's the only one that makes Google Voice a dark gray color for me, when i go on another rom for example, its light colored.
[Verizon Samsung Galaxy S III] PetRiLJoe:
I'm not quoting anyone but I posted earlier that my CPU 1 did not show up on r71. After a reboot it fixed itself. But I will say I am not digging 71 it keeps locking up if I open too many applications where previously it wasn't an issue.

I'm just reporting my experience, I know I can flash back to an old version.

Thanks all.
[Verizon Samsung Galaxy S III] Ryezen:
GPS Woes

I've been running Synergy since the first release, but ever since it went through that GPS transition a while back, I've never been able to get a lock with Maps. I've done a COMPLETE wipe, using ODIN to go back to total stock (no root, locked bootloader, etc.) and even in that mode it couldn't lock with Maps. Even reflashed original radios and recovery. No dice.

Only way I can get lock is to use GPS Test or GPS Status to get lock first, then quickly open Maps.

I read that a couple other users have had this same problem after they had been running Synergy. Most have returned their phones for a replacement, or plan to. Really hoping to avoid that.

I'm trying a custom GPS config file now; fingers crossed.

If anyone has a suggestion, I'm all ears.

~Ryezen
[Verizon Samsung Galaxy S III] xXJay_RXx:
I had to return mine for a replacement. Works fine now. Maybe that's what you need to do. It was no hassle at all. Just relock boot loader and return to stock when they send you a replacement. It was simple
[Verizon Samsung Galaxy S III] azbobs:
I reported this last night as well

and placed a screenshot showing cpu1

showing no activity cpu0 is pulling all the load. I reloaded r60 due to r70 was not good and that is when I checked and also

noticed cpu1 not running.

Sent from my

S3 smokin fast on Synergy r71

: )

Cheers
[Verizon Samsung Galaxy S III] addictedhacks:
+1 My poor S3 is doomed. :(
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Finally. More users that experience the issue that I have. Every time I report it it gets buried in the thread where no one see's or notices it. Hope this will be fixed some how because thats why I think my phone is a little laggy.
[Verizon Samsung Galaxy S III] addictedhacks:
+1 Are you kidding me? I have been flashing this ROM since it was 1.2 in hopes of a release that just worked. Every time an update came out it only got worse. I would report the issues and they would end up getting bombarded by offended people saying how I was wrong and I screwed up my phone and how great the ROM was running for them even though I read other reports of people with the same exact issues. But like you said reports of issues would just get buried and no one would know about any issues people were having.
[Verizon Samsung Galaxy S III] Kawirider1228:
+1 I'm not seeing horrible lag but there is a shutter that I notice at times.
[Verizon Samsung Galaxy S III] bgolden84:
I started running aokp because I could not handle this run away thread any more. Its not E's fault it is a great rom. But some of the users need some common sense. If you have an issue. Reproduce said issue while running a log cat from adb. Then post it to paste bin and provide E with a link to it. Much better than saying x does this and y does that. Each phone will differ from another. It helps developers to have a log cat so they know why you are having the issue. The other option. Fix it yourself

And stop spamming the thread with useless chatter for Christ sake this thing is huge. Most of it pointless.

End rant
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yes I have only had this phone for about a week now and this was the first TouchWiz ics rom I flashed. It felt so fluid and smooth up until now it doesn't feel the same. I'm not hating on the rom or anything, I'm just stating from my personal experience with it. I've tried AOSP first but didn't like it because it reminded me of my Gnex and I thought TouchWiz just looks more polished to me. So I won't be leaving this rom for any stable AOSP rom out there because I am in love with TouchWiz now. I just really wish this problem can be fixed ASAP.
[Verizon Samsung Galaxy S III] addictedhacks:
Deleted
[Verizon Samsung Galaxy S III] bgolden84:
I'm not picking on any one person. I peeked in here to see what the progress was since I last flashed this ROM. R52. And was like 150 pages. Holly hell. Its almost all chit chat. Y. Y u no shhhhh
[Verizon Samsung Galaxy S III] addictedhacks:
Ehhh... Are you contributing to the chit chat? I am just kidding man...:p
[Verizon Samsung Galaxy S III] azbobs:
Lol,

Sent from my

S3 smokin fast on Synergy r71

: )

Cheers
[Verizon Samsung Galaxy S III] dan_joegibbsfan:
E,

If there is some process for log files that will help development please let me know what it is. If you would like to PM me about it I understand that as well. This thread is crazy and I normally don't comment but I know how log files will tell what is truly going on.
[Verizon Samsung Galaxy S III] evolishesh:
anyone knows if this kernel supports the 64gb sandisk card? I'm having issues with mine.
[Verizon Samsung Galaxy S III] prdog1:
Mine working fine with TWRP and formatted fat32.
[Verizon Samsung Galaxy S III] evolishesh:
My phone dose not give me the option to format it. It only says card is safe to remove. Any ideas?
[Verizon Samsung Galaxy S III] prdog1:
Format on PC with this app.

http://fat32-format.en.softonic.com/
[Verizon Samsung Galaxy S III] evolishesh:
i'll try that. Thanks
[Verizon Samsung Galaxy S III] goldsmitht:
how is everyone checking if there is activity from CPU1? I know i can watch it in System Tuner, and it doesn't show any activity, but i also know, that by just watching it, it isn't going to pull enough cpu to make it move. I know mine is working, because when i launch system tuner, i can see it go down.

is there an app, setting, or something that will show a graph of usage?
[Verizon Samsung Galaxy S III] prdog1:
You can pull down notifications and see it move or play a floating video over the top of System Tuner. Should be an app that will graph it but haven't found it yet..
[Verizon Samsung Galaxy S III] voodoomanx:
Click on times in system tuner and it will show you the time each cpu has spent at what clock.
[Verizon Samsung Galaxy S III] itzwolf:
This is what I did to verify it turned on and off as needed.
[Verizon Samsung Galaxy S III] jaredhundrup:
I've been running fine on r68 as well, with random reboots happening. This morning when plugged in it kept doing the reboot probably 5 times in a row. I finally shut it down and will see if it continues. I have not been able to dirty flash even with clearing cache as every time I do, the first thing I notice is gmail won't sync any longer. I've tried all the obvious and no luck so I end up doing a full wipe and install each time I upgrade. Other than the random reboot I'm happy on r68 and will be holding for a short period before another wipe.
[Verizon Samsung Galaxy S III] sherdog16:
micro cpu monitor...it's what you want
[Verizon Samsung Galaxy S III] eschelon:
Will have a new kernel later today. We'll force the default frequency on boot to be 1.5 instead of 1.9 along with a few other changes to see if it fixes random reboots
[Verizon Samsung Galaxy S III] pschatz12:
E,

Will this be the default kernel in tonights nightlie?
[Verizon Samsung Galaxy S III] eschelon:
It will. I've been running this build since yesterday and it's been working fine for me so it's time to roll out to a larger test pool. Hopefully it's an improvement for everyone as ROM stability is my number one concern.

I will still leave the flashable kernel.zips in the OP if people wish to change to another version.
[Verizon Samsung Galaxy S III] bryantwc1:
Please add brightness slider to the to do list too.
[Verizon Samsung Galaxy S III] drbveb88:
Also dalvik cache, it's under advanced in recovery. I also like to wipe data/factory a couple of times just to make sure that all the old files are gone. It only takes an extra couple of minutes but can save you headaches later. Happy flashing! :)
[Verizon Samsung Galaxy S III] baudi11:
Thank you. There's quite a high barrier to entry for people coming to this fresh, even when you try to read all the pinned posts and do your due diligence searching for answers. Not complaining. I don't see how else it could work. Just an observation.

Thanks again.
[Verizon Samsung Galaxy S III] eschelon:
It is

Also, you guys are gonna hate me but I figured I'd give a heads up... The next update will be smaller and will be a simple flashover that won't require a wipe. (Yay)

However, the build AFTER that will be a full re-base to LG1 and that will likely need a full wipe again. Sorry to do that to you guys, but after that LG1 re-base all of the tweaks and major changes should be in place for now and so we shouldn't need any more full wipes for a while after that.
[Verizon Samsung Galaxy S III] Jacquestrapp:
There is a flashable ZIP file out there called "Superwipe" (by a dev named Ohsaka IIRC) that, when flashed, wipes all the data you need to wipe when preparing to install a new ROM on your phone. It's only one step and makes poking around in various recovery menus unnecessary. Does anyone know if that ZIP would work on the GS3, or is there a similar ZIP available?
[Verizon Samsung Galaxy S III] dvaderx:
you only need to wipe once (in the case of roms/cache) :)

it's not like a single wipe will leave something behind.. a wipe is a wipe is a wipe.

this was confirmed and discussed by CVPCS

If you are OCD and feel the need, then by all means, i understand. but know that it's not doing anything.
[Verizon Samsung Galaxy S III] eschelon:
DO NOT FLASH THAT!

If it's the older one I think you're talking about the mmcblcks are different and you will cause yourself issues.

If we get some time maybe we'll throw together a Superwipe for the SGS3. My requested feature list from you guys is already pretty long tho and I'm only one guy ;)
[Verizon Samsung Galaxy S III] drbveb88:
Sorry I forgot..wipe system as well.

And your welcome, always glad to help.
[Verizon Samsung Galaxy S III] drbveb88:
Your doing amazing..thanks for everything your doing.
[Verizon Samsung Galaxy S III] gzsmooth:
Could I use Beans center clock mod without breaking anything? And thanks for the awesome ROM, just donated!
[Verizon Samsung Galaxy S III] drbveb88:
To each is own..It was just suggested by aanother developer when I was on my rezound and since then I feel I have had better results.
[Verizon Samsung Galaxy S III] niv3d:
Hello guys! I am new to Verizon from Sprint (why didn't I do that a while ago?!). Anyways, I'm about to root my SG3 and install a recovery, then install SynergyROM! Few questions...

What is the recommend rooting method?

IMEI, is that really only necessary to back up if I plan on flashing an AOSP based ROM?

Also, are there any issues using TWRP? It seems everyone is using CWM, but I do prefer TWRP.

Thanks for any responses, i'm sure i'll have more questions!
[Verizon Samsung Galaxy S III] baudi11:
How do I do that? I don't see a "wipe system" option on the main menu or on the advanced menu.

Do you mean "format /system" on the Mounts and Storage menu?
[Verizon Samsung Galaxy S III] clambert11:
I really appreciate the heads up on this. I kinda got burned installing SynergyROM for the first time and then realizing 1.3 came out just after. It's no big deal though.

Do you have a rough ETA of when the LG1 re-base will be out? I won't hold you to it but I think I may just hold off until then. If you think it might be awhile, which is fine, I may just update to 1.3 anyway.
[Verizon Samsung Galaxy S III] mb27:
Shoot, no need to apologize, 1.0 just came out 5 days ago - tough luck for them if anyone has a problem doing a full wipe this early on.
[Verizon Samsung Galaxy S III] NAU420:
Yeah I would like to know about this too. I have a few custom icons I would like to use with Touchwiz.
[Verizon Samsung Galaxy S III] jasonxlee01:
Is it just me or all the notification and ringtone sounds gone in version 1.3?

Edit: Nevermind lol they're there now. That was weird.
[Verizon Samsung Galaxy S III] baudi11:
Full Wipe Defined

OK, so a "full wipe" is accomplished as follows using ClockWorkMod Recovery.

1. wipe data/factory reset

2. wipe cache partition

3. advanced > wipe dalvik cache

4. mounts and storage > format /system

Anything else?
[Verizon Samsung Galaxy S III] Schaweet:
All I have ever done is step 1 and have never had an issue with any rom before. I can see maybe doing step 4 but 2 and 3 are redundant if you do step 1. At least that is my understanding.

Sent from my SGS3
[Verizon Samsung Galaxy S III] goldsmitht:
thanks, works, but sometimes hard to tell if there is two lines or not; went with free, am guessing pro (paid) version is more customizable and would make it easier to see

thanks!
[Verizon Samsung Galaxy S III] Coderedpl:
Anyone?
[Verizon Samsung Galaxy S III] AdamHLG:
I wanted to share my experience with this ROM if it helps anyone.

My history is as follows: Root via Odin to Route66, and then to NoSympathy, a few months ago. Nothing since then until I unlocked phone with EZ-Unlock 1.2 from the play store and installed R68 of this ROM. In other words, no prior versions of this ROM or any other ROM until R68 of this ROM as my first edition of Synergy.

I bring this up because I have NO issues at all. I have been running for 3 days now and never had a random reboot, I have no GPS issues, and I have no issues whatsoever. The ROM is fast and stable for me. I do notice that CPU1 seems to be "offline" most if not all of the time but my phone is fast, responsive and lag free. So I don't know what's up with that issue but will watch the thread moving forward.

I am left wondering if the issues some folks report such as no GPS locks or reboots stem from earlier builds of this or other ROMS where maybe some latent files or other changes remained on the phone despite clean flashes or Odin flashes? I am not doubting at all that folks have issues, but I am trying to theorize what might be the cause. If nothing else, I am posting because this is a great ROM for me and if you are on this thread visiting for the first time, and you are considering taking the plunge, this is my experience. Of course, these are nightlies. I can only speak for R68.
[Verizon Samsung Galaxy S III] prdog1:
1.7 to 64 using sept1 kernel and full wipe and flash. Also no issues or reboots.
[Verizon Samsung Galaxy S III] Neverendingxsin:
I can feel a new synergy based theme being released soon ;)
[Verizon Samsung Galaxy S III] t0adman:
Yooowch! r71 and battery is crushed! I also tried micro CPU monitor and I only see one little line darting across the top. I've been out of the loop for a bit - sorry.
[Verizon Samsung Galaxy S III] Juroid:
Has anyone noticed a battery drainning much faster on r71? I updated from r60 to r71 yesterday and I have couple of issues. First of all, battery drains much faster and the other is phone freezing including app force closing. Seems like r60 was more stable.

I did a complete wipe when I installed r71 yesterday. I also have Dark Horse theme over the r71.

Sent From Galaxy S III (i535)

Using Xparent Blue Tapatalk
[Verizon Samsung Galaxy S III] rocketj:
I'm on r64 and I'm not seeing this.
[Verizon Samsung Galaxy S III] ylexot:
It looks like most of the battery use was the screen. How much screen time do you have? What screen brightness?