yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] enix316:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Pretty sure you either have to live with the lag or use the lock button to wake the device. I tried using tasker to workaround this but everything I came up with was worse than the lag.

Personally I deal with the minimal lag, my muscle memory wont let me use the lock button.

Also, I have used screebl in the past and tasker to detect when the phone is upright (and probably being used) to avoid having the screen go off.
[Verizon Samsung Galaxy S III] ylexot:
I use the home button to wake and it returns me to the app that I have open, but maybe it's because I use Nova launcher?
[Verizon Samsung Galaxy S III] Skyroket:
Did you disable double-click in S Voice? I tried with Nova Launcher (I normally use Apex Launcher) and it behaved the same way I describe, when disabling the double click home feature from S Voice.

We need a way to intercept the home click entirely. I think I'm gonna have to start learning how to program a little.
[Verizon Samsung Galaxy S III] fasheezy:
Also, BT streaming was intermittently staticky. Again, I did a Superwipe before installing Synergy. I use my BT speaker almost everyday so I this was a deal breaker for me. I went back on CleanROM 5.6. I wish I could have the multi-window functionality, but I'll take rock solid stability of all features for now.
[Verizon Samsung Galaxy S III] Skyroket:
I had this whenever I used Ziggy kernel. People say to increase voltage, but I took one look at it and didn't want to fry anything or try to figure out at which frequency I needed to set which voltage. I just dirty flashed it and chose stock kernel. Static solved.
[Verizon Samsung Galaxy S III] prdog1:
Can increase all voltages a step at time till clears up. Stock min voltage is 1050. Or can raise any of them below 1050 individually. Raise ziggy's as much as needed up to that. :cool:
[Verizon Samsung Galaxy S III] NeWCuLTKiNG:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Thought stock was 1150?
[Verizon Samsung Galaxy S III] prdog1:
1050 or 1150 don't matter. As long as don't go over that your not over volting. And should not need more than 1000. :cool:
[Verizon Samsung Galaxy S III] eheinzeiii:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

So I tried both apps and my GPS still takes forever to find me and constantly loses me during navigation and its not cool lol since I'm new to the area I live in and the GPS is my best friend lol.. thanks for any help
[Verizon Samsung Galaxy S III] corbn89:
Just wanted to say I was able to recreate that bug. It is probably from multi window since I get that bar when I enable multi window split screen. Doesn't seem to hurt anything, just a visual bother.
[Verizon Samsung Galaxy S III] dogredwing1:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

It look like another way to enable multi window.
[Verizon Samsung Galaxy S III] soopervoo:
Dl GPS TEST from play store and let it run for 20 mins with the screen left on.

Once it locks, you should have quicker and stable connection
[Verizon Samsung Galaxy S III] prdog1:
I played with it a while back and acted more like a recent app button. :cool:
[Verizon Samsung Galaxy S III] donebrasko:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I think I found what's killing the battery. Now how do I fix it?

I have system tuner but I can't change the voltage. Couldn't change it in setcpu either.
[Verizon Samsung Galaxy S III] prdog1:
You got something bad beside the voltage. Your cpu is locked at max. May be the governor. I use on demand. Or you just have something locked in logic. Try wiping dalvic and cache and reboot or wipe dalvic cache and systen and dirty flash. Myself I would wipe everything and start over. If can't change voltage in system tuner it has to do with whatever is locked up if using Ziggy. If using stock or another custom kernel such as lean kernel may not be able to change voltage at all or without doing something else. :cool:
[Verizon Samsung Galaxy S III] donebrasko:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I am on stock should I dirty flash to ziggy
[Verizon Samsung Galaxy S III] prdog1:
You can. I run Ziggys. If on stock make sure you don't have power saver enabled. Still looks like it stuck. Should have more frquencies enabled except for 1.5. Even power saver would be lower than 1.5. Your showing Galaxy Nexus in sig. Hoping you didn't flash on that or you borked something with wallet or have something left over from AOSP base. :cool:
[Verizon Samsung Galaxy S III] AtariDroid:
Has anyone figured out how to get rid of it? I'm assuming this is the same "ugly bar" that shows at the top of some apps in multiwindow?
[Verizon Samsung Galaxy S III] mrkylew:
Crashing

ROM: Synergy-S3_31Jan13_0412_r326_s

After I flash this tons of apps crash.

#1 "Unfortunately, the process com.android.phone has stopped.

#2 "Unfortunately, the process com.sec.sprextension has stopped.

(After Typing in Wifi password)

#3 "Unfortunately, the process com.android.phone has stopped.

#4 "Unfortunately, the process PDroid Manager-TrevE Mod has stopped.

(After Connecting to Wifi)

#5 "Unfortunately, the process com.sec.sprextension has stopped.

ETC. They're quite persistent errors.

I've had this issue on multiple set ups of the rom. Wipe and Superwipe, Default Install, Custom install w/ Ziggy and Stock Rom. I've tried unchecking all the mods.

Any advice would be great.:crying:
[Verizon Samsung Galaxy S III] prdog1:
Have no clue if on Verizon. sprextension is Sprint and has known bugs they are working on. If you are Sprint can't help. I flash it multiple times a day. Only thing I can think of is full wipe of all. Don't save any data. When restore apps restore app only with no data. Make sure you are running latest version of your recovery for your device so you get correct rom. Aroma looks at recovery to flash correct rom for device. If running the 5.0 version of CWM will get Sprint rom on Verizon. I use TWRP. It is only recovery that is consistent in my book. :cool:
[Verizon Samsung Galaxy S III] pprice520:
try it yo, ****.
[Verizon Samsung Galaxy S III] mrkylew:
I am on verizon, so sounds like you're right that I screwed up on that front.

I flash it on full 'super' wipe, so everything is gone. I don't do any restoring of apps.

I'll look into changing to TWRP after I figure out what that is. :D

Thanks for the tip, now I have something to go off of.
[Verizon Samsung Galaxy S III] prdog1:
TWRP is the other recovery. Has full themeable touch GUI with ability to name backups at time of backup and exFat support. In my opinion it rocks. Get GooManager from market and flash TWRP by hitting menu button and picking update recovery script or whatever looks close to that. I'm testing mods so don't have in front of me or flash latest CWM 6.0 series for Verizon. You are running the original Sprint CWM we used to root on day one of device release. That is why you got Sprint version of the rom. :cool:
[Verizon Samsung Galaxy S III] Nckmsn:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Does anyone have a link to adobe flash? Thanks in advance!
[Verizon Samsung Galaxy S III] im_on_fire:
So I clean install r326, stock kernel, with the boot up scripts included.

Reboot. Setup phone. Reboot. Restore backups. Reboot. Everthing running fine.

Change lockscreen settings and enable AOSP lockscreen. turn screen off.

Attempt to turn on. Button lights illuminate but screen stays off. Buttons stay lit for several minutes.

Off center warning message appears that something has forced closed. Can't read it. Screen goes black. Couple of minutes later same warning flashes.

Pull battery and restart phone. It boots to an off centered activation screen the restarts. Boot loops like this for awhile. Pull battery.

Turn on phone again and it just sits on the "android" screen.

wtf
[Verizon Samsung Galaxy S III] NZitney:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Aosp lock screen is not working on 326. I'm pretty sure a dirty flash with stock lock screen chosen fixes it. Read back a bit. It's been discussed
[Verizon Samsung Galaxy S III] cynikalJ:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

You probably just need to turn off ripple effect on the lock screen and all should be well
[Verizon Samsung Galaxy S III] NZitney:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------

Aosp soft bricks device. He can't boot in order to change settings.
[Verizon Samsung Galaxy S III] prdog1:
One more time. AOSP lockscreen is BROKE!!!!.:p:laugh::cool:
[Verizon Samsung Galaxy S III] im_on_fire:
Could we have a warning note in the OP about something that breaks the ROM entirely?
[Verizon Samsung Galaxy S III] prdog1:
Should always read back from end at least 10 pages on any rom. :cool:
[Verizon Samsung Galaxy S III] im_on_fire:
As someone who has been following this ROM since day one, I've read almost every single page. Sometimes you miss something.

Still, a warning about a ROM breaking feature could only be beneficial.
[Verizon Samsung Galaxy S III] ylexot:
Let me Google that for you...

http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html
[Verizon Samsung Galaxy S III] prdog1:
There is close to 75 posts of complaints with the AOSP lock screen since last build :cool:.

---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------

:laugh::laugh::laugh::laugh::laugh::cool:
[Verizon Samsung Galaxy S III] arl16:
http://www.androidrootz.com/2012/08/how-to-install-adobe-flash-player-on.html
[Verizon Samsung Galaxy S III] im_on_fire:
And maybe if there was a warning in the OP there wouldn't be
[Verizon Samsung Galaxy S III] prdog1:
OP hasn't been updated in 1500 pages. As one who has read all and kept up with the thread you should have known that. I have never used or wanted to use AOSP of any kind and knew because I have read all 1740+ pages. The OP on this rom is where new build starts. Search the build number and you will find Ech"s OP or search Echelon or any of us others to see what's up. You haven't read as much as you state or would know how to work this thread. The original OP is NOT going to be updated except for the latest build link. :rolleyes::cool:
[Verizon Samsung Galaxy S III] silenthatred:
LOL to this logic and that attitude in general...I'm going to go out on a limb here and say even if you have read every post of this 1740+ page thread (which I seriously doubt is true, (and for human sake, I hope is not true) but let's assume it is) that you don't remember everything posted in it. If something is known to give problems, and it isn't something that is expected to, or hasn't in the past, it probably should be posted in a place where people will see it, other than "reading 10 pages of posts." I mean think about it, why would I search or look for something broken that wasn't broken before or something that doesn't normally break, nor should be expected to normally break?
[Verizon Samsung Galaxy S III] thornev:
Sorry, Man, but I have to disagree with you on this issue. Expecting readers to follow an unusual process (in that hardly any other developers if any at all) of looking for links to mid-thread posts about ROM issues is unreasonable. Most readers (well I can't really speak for everyone else, can I?) expect such issues as this to be posted in the OP and that is the best place for it as was pointed out to avoid "75 posts" on an issue. I know not everyone reads the OP, but scattering important ROM info throughout a thread that's thousands of posts long is just going to increase the likelihood that people will miss that info.
[Verizon Samsung Galaxy S III] Schaweet:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I get the point of it should be in the OP. That does make sense. I think the point prdog is making is that this guy's says he's read up on the thread. If that truly were the case he would have known AOSP lockscreen breaks the rom before he tried it. He also could have read a few pages back after he broke it to see AOSP lockscreen was the culprit.

It's true it would be nice if that was posted somewhere, but to be totally shocked by it is just simply being lazy. Also flashing a rom to your phone without reading or at least skimming the rom thread is criminal.

Sent from my Synergized S3
[Verizon Samsung Galaxy S III] thornev:
Not skimming 17,000+ posts is criminal? The guy's statement aside that he's read the thread since day 1, for someone new coming to this ROM, I don't know about anyone else, but skimming 17,000+ posts looking for possible ROM problems is crazy. Having said that, I certainly do peruse threads when I try a new ROM, but I simply don't have the time to skim 1742 pages. And this issue would be moot if the critical ROM info were in the OP (for the moment excusing those people who don't even read that).
[Verizon Samsung Galaxy S III] donebrasko:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I understood a lot of what you said.... I think. I dirty flashed ziggy. I can now adjust the voltage. I dropped it to 1000 something. I'm going to see how it works. Thanks
[Verizon Samsung Galaxy S III] im_on_fire:
i also said that i miss things for time to time, because i have to skip over unhelpful converstations that take up space like this on going one we are having.
[Verizon Samsung Galaxy S III] matthew.fiore:
agreed.

it was be very helpful to have a section in the original post labeled "Not Working:" that lists all the known bugs.

since this thread is so long, this would cut down on the repetitive posts.
[Verizon Samsung Galaxy S III] Schaweet:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Are there 17,000 posts since 326 was released? No there aren't. Your logic is flawed.

Anyway.......back on topic. I'm done here.

Sent from my Synergized S3
[Verizon Samsung Galaxy S III] dems86:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

While I somewhat agree with your point...it is far from a stretch believing that someone has read this whole thread. Reading the couple new pages of posts each day barely takes a minute or two for someone of average intelligence. There was probably a better way to make your point. For human sake I really hope the majority of members don't balk at the minimal amount of time it takes to read through a few pages of a thread.
[Verizon Samsung Galaxy S III] HoudiniJr:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Back from a long hiatus :cool: I like this idea, think it would help a lot of people. Though there will still be a ton of people who still wouldn't read it, could cut down on something's.

Maybe opening up a synergy support thread wouldn't be such a bad idea :) but then no one would probably use it anyway so guess not haha :rolleyes::D

Sent from my Secret Base in Outer Space
[Verizon Samsung Galaxy S III] prdog1:
Yall are funny. If knew what you were doing would know that the AOSP lockscreen has always been broke or not worked fully and correctly to some point on all ports to Sense and Touchwiz since the first time it was called a Honeycomb lockscreen. :laugh::laugh::laugh::cool:
[Verizon Samsung Galaxy S III] M_T_M:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Aaaand this is where I get involved. If you or anyone else does not like the way this ROM is being developed or maintained.....go someplace else mate.

Cheers,
[Verizon Samsung Galaxy S III] tducote:
Keyboard defaults back to Samsung

I know this was brought up a while back, but the keyboard seems to always reset from SwiftKey back to the Samsung keyboard after a reboot. What's up with that, yo?
[Verizon Samsung Galaxy S III] Schaweet:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Has Never happened to me. I guess I'm lucky?

Sent from my Synergized S3
[Verizon Samsung Galaxy S III] tducote:
Are you using the Market version of SwiftKey? I've heard this doesn't happen with the SwiftKey Flow beta.
[Verizon Samsung Galaxy S III] bfs673:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

+1

Too many Devs have been driven off by an ungrateful few.

I, for one, REALLY appreciate the developers and community support.
[Verizon Samsung Galaxy S III] doodlebro:
If you even read what I said, I didn't say anything against the devs of this ROM at all. Does it address devs in general? Sure, but I'm not driving off devs by backing up the idea that a list of features that break the phone if enabled is a pretty easy and helpful thing. Especially for those of us who are moving from one phone or manufacturer to another.

Did you read what I said, at all?
[Verizon Samsung Galaxy S III] pprice520:
Back to the synergy rom!

I love it

ive flashed it on verizon i535 works flawlessly (for the most part) (typical "flashable rom)

thank's synergy team!
[Verizon Samsung Galaxy S III] Schaweet:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Ah that's why. I've been on flow beta since flashing 326. Good to know.

Sent from my Synergized S3
[Verizon Samsung Galaxy S III] enix316:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I just switched to flow version. Had been using SwiftKey 3 or whatever it was prior. I never noticed this problem.
[Verizon Samsung Galaxy S III] huskyjayboy:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

same here
[Verizon Samsung Galaxy S III] Camborg80-Trey:
Super noob question guys, sorry.

Do I have to do a full format of data/cache/dalvik (and lose everything so I have to back it all up) if I apply the latest version of Synergy? The one i have now is like a month old.

I want the latest and greatest version but it'd be a bit of a pain to have to do that everytime. Can I just install it on top of the one I have or is that a big no-no?

Cheers and thanks!

:o
[Verizon Samsung Galaxy S III] neh4pres:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

This is a age old question that won't go away.... do whatever you want. The suggested method is already set in stone.

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] DieselNY:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I switched to twrp last month and its leaps and bounds better than cwm. For those hesitant or just too lazy to switch it's totally worth it.

---------- Post added at 09:11 PM ---------- Previous post was at 09:03 PM ----------

Is there a new build coming soon maybe to just clean up some bugs? My phone still randomly shuts down requiring a battery pull. Often it is during or right after a call. r326 was flashed from super duper wipe..clean like wiping a baby's butt.... Fixed permissions many times. Didn't install app data. Dirty flashed over a clean wipe to see if it fixed. Many cache and davlik wipes but still get a reboot atleast once a day. So instead of doing another wipe from scratch I'm curious if a new build is around the corner.
[Verizon Samsung Galaxy S III] prdog1:
New build coming but sounds like you just need to increase voltage. :cool:
[Verizon Samsung Galaxy S III] DieselNY:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I went up to 1000 few days ago. Where should I cap it?
[Verizon Samsung Galaxy S III] adlakeche:
Have to say you are really going out on a limb. Not sure what you guys expect, remember Esch and team are developing a rom that the carriers haven't even put out yet. You should expect things to not be perfect. Everyone here can put in input which helps make it better. When I flash and have a problem I head right to the top of the page where it says "SEARCH THREAD". Seems like most forget that and just want a quick answer so don't have to work on finding it. For instance an "AOSP lockscreen" search would have given you a multitude of answers to find your solution. As for prdog1 reading every page I am pretty sure he has. He's been a big help to a lot of you. I've read every one since August 2012. Takes me about 10 minutes to catch up when I get home each night.

If you want a perfect running stock rom with no bells and wistles, I suggest to ODIN back to stock and enjoy.

If you want a lot of extras that are not available anywhere but with Synergy then hang around. There's gonna be bumps in the road so expect them. These guys do a hell of a job..:cool::cool::cool::good:
[Verizon Samsung Galaxy S III] rwc95:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I had to go all the way to 1050 on ziggy to keep from getting sod. I've only had to on 326 build all other synergy I was able to stay at 900
[Verizon Samsung Galaxy S III] DieselNY:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I went up to 1050 and 20 minutes later phone rebooted again lol.
[Verizon Samsung Galaxy S III] donebrasko:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Nope I'm on my second full charge of the day and I have watched my phone drop from 17% to 13% since reading through these posts. Now 11%
[Verizon Samsung Galaxy S III] prdog1:
If you are that high I would reflash with stock and see what happens. If no problems. I would reflash Ziggy again. 1050 should be enough on any device. :cool:

---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------

Do you have G+ syncing photos. Looks like a lot of Gallery time. You have apps going rogue but you got everything you can stream streaming. Are you using back button to exit apps. If using home button to exit every app you access is still running in the background. Home exit of app is to keep app active for multi tasking. :cool:
[Verizon Samsung Galaxy S III] eueyj:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

I was having reboots as well normally after a call as well. I ended up dirty flashing stock kernel and my phone is running well. Before I dirty flashed I superwiped etc.

I know I miss out on some of the features ziggy offers but with the stock kernel I haven't had any reboots or force closes.

---------- Post added at 05:08 AM ---------- Previous post was at 05:02 AM ----------

I mean I superwiped and installed with ziggy kernel then I dirty flashed with stock kernel.
[Verizon Samsung Galaxy S III] DieselNY:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★

Hmm I did not want to lose the ability to use my 64gb exfat which only Ziggy seems to have a kernel that works with one.
[Verizon Samsung Galaxy S III] Nckmsn:
Re: ☆ ★ | ROM | SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-31-13 r326 |★
[Verizon Samsung Galaxy S III] eschelon:
Already got this built into v1.5

As they continue to improve on Google Now we'll keep updating it.
[Verizon Samsung Galaxy S III] racinwarrior:
youre a beast bro
[Verizon Samsung Galaxy S III] baudi11:
Ah. Now I see. It's not available in Go Launcher, only in TW Launcher. I wonder why...
[Verizon Samsung Galaxy S III] drbveb88:
Does anyone know where the gmail apk is in this rom? I looked under root explorer and can only find the email exchange and email apk.

I am trying to push the inverted version of gmail, would there be any bad side effects from doing this?

Thanks for the help, this xda community rocks!!!
[Verizon Samsung Galaxy S III] gzsmooth:
my phone always does this but goes off about 5min after sitting on 100%
[Verizon Samsung Galaxy S III] d1ez3:
Is it possible to add power save mode in the quick launch bar? I don't see it as an option to add in.
[Verizon Samsung Galaxy S III] eschelon:
/data/app/