Synergy-S3_25Feb13_0527_r373_s.zip (MD5: 9fb7152fa1be83d7b97a386cc8d170cc)
http://beta.androidfilehost.com/?fid=9390331926465740974
Pretty significant changelog in this release, so hopefully things are pretty stable for you guys. First, the thanks. Yea I know it's like getting a present with a card attached and nobody wants to read the card so you just pretend to skim over it before you get to the good stuff, but a lot of people really spent a lot of time on this update making it run better than ever before and they deserve props. As you know TrevE finally got his hands on a device and has been going on a tear adding new toys and cleaning up TONS of issues on the back end. He's always been a great asset to team Synergy; we're lucky to have him around. Same goes for Ziggy. He spent two weeks flashing a hundred times a day (no exaggeration) to get his S3 kernel running better than anything I have ever run in the past. You guys should see insane battery life on this release. Also check your deep sleep times and be amazed with his work. There were so many others who pitched in this ROM (Didact74 again) as well as a ton of you for testing. I wish I could name you all personally, but you know who you are. Thanks for helping us work out the bugs with this release.
For starters, Samsung and the carriers have all sorts of checks on the back end to see if you're rooted, running a custom ROM, or have made any modifications to /system. Often times Android devs (us included at times) will do a mod and as soon as it works, they run with it. But there are numerous instances in which stuff is broken behind the scenes and you don't even know it. This build includes some serious patches on the back end which make things run properly and phone home correctly without raising red flags to Samsung or your carrier. TrevE has a post here with more info (
http://xdaforums.com/showpost.php?p=38444474&postcount=17932). Point is: You can trust Synergy to be clean, secure, and free of any behind-the-scenes nonsense.
Now to answer the questions I know you're already gonna ask: Ink effect is now sorta fixed (all colors work, including the 'none' option, but the color flash still happens. We took a long look at this one and it's still evading us at the moment. The math they use in the ink effect is weird...
Glance view: We have (and actually have had for the last several builds now) the framework working to support this. In fact we were able to kick it off with adb commands at our will, but hovering your hand over the sensor didn't quite work and it's actually gonna be a nasty hack to get fully working. We're still looking at it, but no promises on when or if we fully get it working.
Also, The reason we asked about your CPU revisions earlier in the thread is because some of you guys are running different revs and they handle voltages differently. Bad news for you guys on rev 4: You can't adjust your voltages. Samsung hard-coded them right into the CPU. You can try to change them all you want, but they aren't going to stick. You're probably stuck with stock. We've added scripting to AROMA which will tell you your CPU revision you have and if you can't adjust voltages, we'll tell you right there in AROMA so pay attention.
Open Pdroid has also been merged into our already existing PDroid capabilities. This is great news for those following the Open PDroid story. Head over here to give those guys thanks:
http://xdaforums.com/showthread.php?p=36678558 You should also be advised that we've changed the way that we install /data apps. They won't start pouring into your app drawer until about 30 seconds after first boot. This is the proper way to do it and will help a lot of you guys out that are seeing problems from dirty flashes. The AOSP lockscreen has also been fixed. In fact, we've forced it so that only the AOSP option OR the ripple effect can be checked at a time - not both. If you want to use one, you gotta go uncheck the other. Ripple is forced by default.
Finally, our AROMA is also significantly improved. Too many changes to list them all out but the biggest things are a new toolbox which you can use to change ROM and kernel settings without having to reflash the entire ROM (w00t) and if you choose the Ziggy kernel on flash you will get a new screen in which you can change frequencies and voltages.
The full changelog for this release is huge. You can see the list of all of our SVN commits since r326 here (
http://www.ziggy471.com/changelog_r372.txt) if you'd like, otherwise you can just check the list of only the biggest stuff below
Changelog - This is only a partial changelog, if you wish to see all commits since the last build then go here (
http://www.ziggy471.com/changelog_r372.txt):
- Improved support for GSM devices
- Synergy now passes all background carrier compliance checks / CSC verification (and still passes the Samsung root checkers)
- Improved activation bypass support (when this option is selected the Setup screen will still load for a few seconds – it needs to do this in order to pass some checks properly)
- Lots of changes to AROMA
- If you choose Ziggy kernel on custom install you will now get a new screen to set OC levels and voltages
- New additions in the form of a Synergy toolbox in AROMA (make changes to the ROM here without having to reflash the entire ROM)
- New options in AROMA for Note 2 keyboard, emoji keyboard, and some other stuff
- Updated all apps, as well as Polaris office from Note 2 (this Polaris is actually pretty sweet, check it out)
- New Ziggy kernel
- Battery icon can be changed on the fly in Settings – Display (Thanks once again to smali master Didact74!)
- Ink lockscreen sorta fixed (screen still flashes sometimes, but all colors work)
- New Ziggy kernel with drastically improved deep sleep functionality
- Added in OpenPdroid support to our already existing PDroid port
- AOSP lockscreen fixed (only AOSP or ripple effect can be checked at a time, not both)
- Over 50 bug fixes
