yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Stryke_the_Orc:
Thread has been cleaned. Keep it on topic and respectful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedolo9y:
Lost WiFi after installing kernal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
This has been brought up a few times. AOKP uses different WIFI drivers and is incompatible with this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Really so they can't use this kernel!? For real?

Task and Ktoon were the team of my dreams back in the day when the gs3 was the flagship... Now both are on the 4 but I still wanted to give the old combo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
how to use fastcharge in a car?

hi,

the fastcharge doesn't work for my S3 d2att, while it's connected in my car to MHL.

I use MHL to output video to car head unit over HDMI, Samsung MHL adapter is connected to dedicated 2A USB car (12V) charger.

Yes, I enabled fastcharge and it works while my S3 is connected to laptop USB, but just doesn't when it goes over MHL :crying:

Anyhow I can troubleshoot this? Any tools / apps that shows charge current for S3?

I also tried Monoprice MHL that is connected to TV and my phone was loosing battery like a 1% per 10 min, while I expected it should get charged.

Anything I'm missing?

thanks for guidance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Fast Charge only works if the Plug is offering higher output. Car Cigarette Adaptor is limited by its fuse. So I highly doubt it will let you without blowing the fuse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
That makes sense. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaY_III:
Your car outlet can most certainly provide enough juice for fast change.

Normal charge is .5amps x 5volts for 2.5watts

True we don't have 100% efficiency so you car charger is probably drawing closer to 3 watts.

If your car could only handle 3 watts we are taking about a 3watt/ 12volts = .25amp car fuse. We know that is not the case.

So if you phone is trying to draw more current, the charger is going to be the limiting factor. Go read the specs and look at it's output. If it's higher than .5 amps you should charge faster then USB spec of .5

Just remember when you look at the rated output on the charger it only produces that when the load (the phone) requests it. So the 1amp it probably is, will only be supplied when fast charge works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehsan102:
hi all

can i use this kernel on my T999 ?

iam using 4.3 official , and i got camera fail problem :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes You can. Make sure to select the correct Touchwiz kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
ktoonsez, I am running the latest kt kernel and it looks like the charging min and max mhz options from ktweaker are not working.

I have my phone set to OC slightly when it is charging, but it looks like the clock speed stay at the default settings. I have enable OC steps checked.

Anyone else using the charging min/max settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Same issue here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
4.4 Kernel won't flash. I get error can't load script in boot.IMG.

Any ideas? I downloaded 3 times all 3 fail to install in twrp 2.7.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
MANY people are having issues with TWRP 2.7.0.0. Try downgrading to 2.6.3.1 found here.

http://xdaforums.com/showpost.php?p=47840637&postcount=758
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
It wouldn't flash on 2.6.3.1 so I updated to 2.7 with same result.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Make sure to wipe Dalvik and Cache before flashing. If you still have problems then Go back to 2.5.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Thanks. Wiping caches did the trick.

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

And now after reboot the notification light wont stop pulsing blue lol any fix for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Plug then unplug your USB and it will stop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Which version of TWRP did you settle on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Problem solved! Thanks. Now onto a bigger issue. WiFi won't enable... Any ideas?

I'm on baseband I747MVLUEMK5

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

2.7.0.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Well the issues are coming out the woodworks on me. Newest kernel won't let me enable WiFi. And now when I go into twrp fix permissions. It fails. I'm back on 1/28 4.4 kernel for now. And 2.6 twrp. 2.6 fails to fix permissions too. It gave me error about /system/app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I assume your wireless works fine with Older Kernel. What Rom are you on ? Quiet possible the Rom is missing Commits from the CM ?

TWRP sometimes may fail to set permissions for a bunch of reasons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Yes my wifi works on the previous kernel version. I'm on slimkat last official build 3.

Maybe if I update my ROM to the newest might help your saying?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sickblutahoe:
Will this work with task650's 4.4.2 kit kat ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No.

Tons of kernel commits merged tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sickblutahoe:
Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes Please update Slimkat to latest Beta.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Updated. Everything is fine now. Including fix permissions. Should I bother updating to 2.7 twrp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
If it aien't Broke, don't fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Can't argue with that!

Thanks again man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 3.24.2014

1. Some ramdisk updates

2. Complete sync with CM as of the commits from 3.22
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Thank you! Was running stock kernel after all those commits. Flashing now. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Working great as usual!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Thanks for the update, Ktoonsez. Will flash shortly. UPDATE: running very smoothly so far.

If you get a chance, can you take a look at the charging min/max settings in the tweaker? They do not seem to be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They work, and I dont have the phone to debug anyway :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
They don't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Flashed latest and no wifi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes it happened to me as well. But I know its my Rom that's probably missing the latest CM Commits. So I am going to wait till the next weekly on my rom to drop. After that I will try this release again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Yeah my Rom hasn't updated in the last week so that's probably it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
This kernel will be BEAST. Me and ktoonsez have been working together. I find him good commits and he adds them to our kernel. When aokp jb comes out this phone will be faster than task's laptop. Lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
I am nor actually on an atrix. I always wipe and fix after kernels updates and I m sure I'm using the right kernel for aokp. The Asop one correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
On AOKP as well, Setcpu showing lowest frequency as 384 on latest AOSP ICS kernel. Wiped caches before and after flash, as well as permissions fix.

But it could have been like this for forever as far as i know, as i rarely pay attention to the low frequency... Just confirming what someone else posted.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Having trouble flashing this on my ps3... can someone help? Im having cod withdrawls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kociubin:
I'm seeing the same thing. I was getting 192 as the lowest freq prior to flashing 7/21. Now the lowest is 384. There is something to this...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Are u serious? Its always been 384 for me... oops never knew that

Edit: o wow. I could have saved alot of battery... i just changed it to 192 in vc :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Is this a sense kernel? :confused::confused::confused:

Lmfao ota battery charging..seriously let me hook up my solar panel wifi enabled home charging device

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I was kidding about the Atrix, lol. And I am sure you are using SetCPU now, for people that insist on using it after I HAVE BEGGED everyone to stop, try clearing the app data for it and see what happens. I can pretty much guarantee Voltage Control will show all the proper steps.

UPDATE:

I use AOKP obviously and just loaded SetCPU and it lets me set it to 192 in that app too. So you need to clear app data for SetCPU or do a full wipe guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
I'm using voltage control...did a full wipe and same thing. Like I said I get 192 when i go back to 7/19c.

Sent from my unlocked Motorola Atrix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Aawww man, i hate arguing with a dev, especially when it comes to his own work, but i wiped setcpu data, and installed voltage control and both are showing 384 as the lowest frequency... Personally i dont really care, just reporting my findings.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Yeah I'm not getting the 192. I had it on 19c but not on the new one. Have flashed with all the steps. Then redownloaded all steps and cleared voltage control data. No problem I think I would stay at 384 anyway. Its supper smooth and great battery life as is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Ditto. I would like to get down to 192, but shouldn't be a huge problem. But I also am not a huge fan of being assumed that we don't know what we're doing. Seems like my problem is being confirmed over and over too. I'm not fully versed enough to make my own kernels and roms but I do know that I have done all proper steps and followed all direction to the T. I guess there are so many other idiots on the board here.

Guess I'll just stick with 7/19c for now since change log doesn't show huge changes.

Thanks ktoonez for all the work.

Sent from my SGSIII.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
I get 192 no problems here. Latest kernel and voltage control. Mind you I don't use it cause I get great battery life with 384.

Question/possible bug maybe even user error lol. I plug in my phone overnight and in the morning it still shows charging, its at 100% but shouldn't it show charged or charge complete or some such? Just a little worried I might be overcharging although I've read that's not possible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
If the rom you are running has removed the charge full notification, you won't see it. Has nothing to do with kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
its not possible to overcharge this device. it has a pretty awesome fuel gauge that will stop charging and start charge depending on what it needs. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Don't know if this is the kernel or ROM, but on cm10 when there's that little loading symbol on YouTube or Facebook, it changes shape a little. Hard to explain, but it does
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
It looks like the download link for the Sammy version is still 7-19c? Is this correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
kernels don't have anything to do with the graphical interface of a rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Okay thanks, must be something with the new build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
How about sound? I use volume+ and dspmanager to boost sound quality and when I do it makes the sound crack and makes a really high pitch screeching sound.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
[MENTION=4325945]ktoonsez[/MENTION]:

Just wanted to check if the TW kernel would be updated with the latest. T-Mobile users have received major Firmware update last week.

Build date: Sat, 08 Mar 2014 10:58:03 +0000

Product Code: TMB

AT&T and T-Mobile use the unified TW kernel from Samsung

Hope we can have updated TW kernel with the latest from Samsung.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You'd have to wait till Samsung Releases the updated Source.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahnkou:
Testing this out now with AOSP rom. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Think Samsung has not released the kernel code for 4.3 for our device, but still we have the kernel in first place.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 3.28.2014

1. Linux 3.4.83

2. Linux 3.4.84

3. CM sync

4. Ramdisk sync with CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
This one may be a no go. Stuck on the KT747 splash screen on boot up. This is with CM11 3/28 nightly.

Flashed kt 3/24 and it booted up fine. I am going to download again in case I got a bad download.

UPDATE: downloaded again, same result
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
File on the server looks good, not sure what it could be, there is 35 downlaods so far so hopefully someone will chime in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Downloading now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
https://github.com/CyanogenMod/andr...mmit/c2e189edf64901d15359c281889e0500448514d1

Seems to break things for some people. At least on my side. Let's see what else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Working fine here. Android is optimizing apps as I type this. Latest CM Nightly, ART.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks, Ill see what happens here. But that would make sense, since that firmware update was meant for Verizon model according to the commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Cooooool, thanks for the feedback :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Touch also working fine. People might want to update their boot loader/modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
+1 on borkage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'm booting alright but for some reason tapatalk is uninstalled and I can install it without it rebooting. Also battery stats a bit borked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You need to update your ROM, there was an update to "healthd" in ramdisk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
You should rename your virtual box, KT. VirtualBox #1 is boooooring ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
going to try the 3/28 release with gummy 3/29 shortly.. will report back.

edit: boots fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
[MENTION=4325945]ktoonsez[/MENTION] resync with CM and release a new kernel. I reverted the touchscreen commit that was causing issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ptl4ever:
[MENTION=4325945]ktoonsez[/MENTION] what are your settings?

Are they still the same as it shows in the second or third post?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You may wish to refer to this thread for more updated information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I havent used it in almost 6 months now, I never have it with me due to traveling for work. In fact if anyone wants to buy it PM me :good:. Need to clean off the desk, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
I hope this doesn't mean you're giving up on us :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, there are still about 600 of you guys using the kernel so I will keep building just like I have been for the last 1+ years :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
I've tried em all but always come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Same. I don't know what it is but this kernel has proven better than the rest multiple times. Quality coding paired with a quality app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chewingum16:
excuse me i'm new here & for stupid question !!! it works for stock rom rooted?? 4.3 if yes ...which link thanks!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes it Works. Look for the Touchwiz link in OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Penguyen:
Does the updated Wi-Fi drivers do anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crypt0kiddie:
Trying to narrow an issue down with my phone. I'm running the Stock Mod ROM 4.3 and this Kernel for TW.

Everything seems OK but Wifi isn't working right. So I got the ROM installed and the kernel and I started reinstalling my apps and the apps store is simply not usable. Talking 20+ minutes for a 5 meg app. I click Wi-fi off and let LTE kick in and the apps almost finish downloading instantly.

Speed tests work as expected though on Wi-Fi.

I don't know if this issue is ROM or kernel based but I'm not seeing others complaining about it.

I Nandroid back to my 4.1.1 stock backup and everything is fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Many people complained about Samsung's 4.3 update. The Stock Mod is based on that. Wireless issues are likely a result of that. You will have to do other steps in order to make Wireless work again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crypt0kiddie:
Well its working it just sucks. So slow! I will dig...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
Quick question... Is the kernel working on Task's latest ROM for the S3 (4.4.2 03/29)??? There has been WiFi incompatibilities and I'm just wondering if this has been resolved... Thanks guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crypt0kiddie:
OK I did some checking and I'm not having the Wifi issues other report as far as it dropping off. It stays on and it's solid. I can serf the web, use Tapatalk etc without issues.

When I try to do things like Youtube or the Apps Store, that is when I notice issues.

Do you know exactly WHAT I should be looking at or what fixes are out there? I tried asking in the STOCK MOD ROM's thread and got nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
This has not and will not ever be fixed. It's been asked 1000 times, and now I'm going to create this post and tag it relevantly so nobody can say. "But I searched!"

tags: task aokp fix WiFi driver
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 04.02.2014

1. Linux 3.4.85

2. Cm sync from last 2 days of commits

3. Revert "input: touchscreen: d2_fw: Update firmware", which was causing the boot issue and no touch for some people
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goombah88:
I get a status 7 error when trying to install this new version. I have the latest 6.0.4.7 CWM Touch installed too.

If you need the exact wording of the error I can try running the install again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No dont need the exact words, its a recovery issue not a kernel issue. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
[MENTION=4325945]ktoonsez[/MENTION] I was wondering what you think about the intelliactive governor and if you could add it in the future possibly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goombah88:
I re-downloaded it, just in case...didn't help. I tried flashing it using Flashify...didn't help. Confirmed i'm using the latest CWM on their website. I've never had this problem on any other kernel install (including the botched touchscreen 3/28 release).

Does anyone have an idea what could be going wrong or how I could get it installed?

I'm using a Samsung Galaxy S3 (AT&T). Anyone else successfully installed the 4/2 release yet?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The latest CWM is the problem, they are moving forward with new implementations that all the other recoveries do not support. If we can find someone on TWRP and an older CWM I can try a script test that the recoveries read and see if it will work on all 3 kinds of recoveries.

So anyone that wants to participate, chime in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I have TWRP 2.6.3.1 So Bring It. :D I am game. Never updated to 2.7.x.x
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok buddy, go ahead and redownload with same link and see if she flashes, it has the same update-binary as Cyanogenmod and I modified it flash the kernel to the boot partition a different way (just like CM).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Gonna try now. Do note, I do not use CM Nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
I'm still using the little over a month old Philz cwm. So I'll try and flash as well. I'm running the 3/29 Liquid Smooth 3.0 nightly

---------- Post added at 02:44 PM ---------- Previous post was at 02:34 PM ----------

Flashed fine, booted fine, running fine. But lost a few apps like root Explorer, which shows I have in the playstore, but when I try to open it, it crashes. Was gonna look at which version of Philz I am actually on. I know it's 6/6.0.4.7,.but.i beleive it's 6.11.2 or something like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Wow, cant believe your recovery deleted apps. Thats insane
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Found it using Liquids Explorer.

Philz touch6.19.3 d2lte

Edit: Flashed my gapps package again and all is well. Had to re download a couple apps from the playstore, but no biggie.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for reporting back. Anybody else flash it yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Not so good News. I wasn't able to flash the Zip. "Error Executing updater Binary."

I did wipe Dalvik & Cache before flashing. Not necessary but did it nevertheless. Now I am not opposed to updating my Recovery. But I believe you wanted me to see with older Recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, I figured that would be the case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
[MENTION=3639717]Perseus71[/MENTION]. Re-download again and let me know what this one does. Also, anyone else feel free to chime in here. Redownload it first then see what your recovery does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Ok On It. Will edit this post back with results.

Flashed Successfully. Optimizing Apps right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
Likewise - used TWRP - latest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys, at least I know it doesnt effect the old stuff (TWRP is using old stuff). We need some CWM guys to test now. Where the heck is everyone!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
Ironically - this has happened before - lost the following apps (removed) - wiped cache/dav'