[Galaxy S III Android Development] KeesStolk:
V37 so far.

First S3.

Flashed the first test Omega 37 as a full wipe and flashed the final v37 as dirty as it can, just let Aroma do some wiping.

I noticed that flashing dirty from beta v37 to final v37, i didn't had the call number bug.

Left the S3 for a 8 hours standby and lost 5% battery, not bad on first load and with stock kernel.

Second S3 (wife's phone).

Flashed again as no wipe from v36 to v37.

But this time i had the call number bug.

As you all know, easily fixed by clear data of contacts and Phone, removed google account, reboot, setting up google account again and Fixed.

Again, all is looking good.

About Triangle Away, bootloader and recovery.

Both S3 have the new bootloader and V37 now.

But the wife's S3 is still using the official 6.0.2.7 recovery, not the one patched by Philz.

Both phones when entered recovery will trigger the counter, red marker and so on.

So, when done flashing stuff, run TA and you will be fine if you use the "old" recovery.

TA and in combi with the "old" recovery will reset all to official, till you enter recovery that is.

But with Philz patched recovery, all will be reset accept the system status, still gives custom.

Flashed back the official recovery, but still gives custom, so no point in going back to none patched one.

In short, if you worried about warranty:

Leave it stock, but you will loose all the fun Omega gives.

Or

Don't flash the new bootloader, although it's looks that the new bootloader has nothing to do with Sudden Death, only made for Sammy to see quickly if you rooted, i am not 100% convinced this is the case.

But TA works

Or

Don't flash Philz patched recovery and remember to use TA every time when you flashed stuff at recovery

As far as i know, this only goes for stock kernels, not for the custom ones.

Or

Just use all the latest and have fun and think about warranty when it comes to that and remember, when living europe, we have some protection from Brussel although knowing Samsung, i will not be easy and they will give a fight.

But i have every confidence that Chainfire and Philz or other great dev will sort this out in the near future.

Just sharing my 5 noobish cents.

Edit:

A little bit annoyed that wifes phone had all official and my lovely S3 was

Custom Binary download: no

Current binaries: official

System status showed custom.

So was fiddling around some to see if i can get it all official.

Flashed bootloader XXALE8 again, used the restore zip Chris_84 provided. Just flashed it from recovery.

Very easy and nice, i did looked at the thread about restoring the bootloader and after reading some stuff, i decided i am still a noob and just use the recovery zip :).

Rebooted, checked with Android System Info if and the flash was successful, was saying Bootloader XXALE8.

Run TA again to reset it all and after done and rebooted, just to 3 combo buttons to go into download mode.

Still got the same, System Status: Custom.

Oke then.

Flashed the official cwm 6.0.2.7 recovery again and see what this brings.

After rebooting a few times and trying TA a few times, still no change.

With this combo, i can enter recovery and flash stuff without triggering the counter.

But this is/was not my goal.

So i used pc odin to flash the latest bootloader again and see what it gives with the "old" 6.0.2.7 recovery.

Again, used TA a couple of times, rebooted a few times etc.

No changes made to system status.

Decided to flash Philz recovery again and still the same.

It's no biggy, but just a bit annoying especially when the wifes S3 all is saying official with the same combo.

The only thing that is different is that i didn't flashed Philz recovery on her phone.

So, next step to compare, flash Philz recovery on wifes phone.

Flashed without problems, rebooted a couple of times, used TA a couple of times and all stays official except when entering recovery, but this a know "problem" with the new bootloader.

Looked at the difference with some system tools, no difference, same chip and so on, only difference is, mine is from 05.2012 and hers is from 06.2012.

So i guess, although they both named S3, both have the same chip, they are not identical.

If anyone can share a light on this, please do.

For now, i guess i just have to wait till some great dev comes up with something.