[T-Mobile myTouch 4G Slide] Blue6IX:
Software number is something the ROM creator can arbitrarily set. I never updated it from the 1.28.531.9 because:

HTC released the 1.28.531.10 OTA - fully two months after the changes they made were done by us here. Further HTC kept their logging tools active, and it took them that long to push that tiny update because they wanted to keep logging your activity - I had long before removed their spyware.

Baseband - (radio)

older radio is 10.48.90007

New radio is 11.59.3504

( I left off the rest of the numbers because aside from 2 work shifts i have been at the s-off issue on our device without sleep since the weekend (and before), and frankly there aren't enough radios to confuse for this device.)

Bulletproof doesn't flash a radio so it will stay with whatever your phone already had on it. People on the newer radio have a wifi issue - i've been back and forth over this trying to peg it all down - I have multiple posts in threads all over the place here laying it out - and I know that's not fair to newcomers.

I haven't had a chance to update the ROM to the new radio - I could compile a new wifi kernel module for it - but there are other ways to fix it. Consider this pending.

Your kernel didn't change because I very loosely used the term kernel in the beginning and throughout the thread, to make it easier and less technical for people.

The truth of the matter is that the boot.img file contains the kernel (ramdisk) and a bunch of other configuration files. Of those configuration files, some of them need to be changed to make it an insecure boot partition. If you want more info on that hit my sticky at the top of dev and look up the boot, hboot section.

Bulletproof (and any ROM) will benefit the end user with an insecure boot image.

That being said - and the difference between boot.img and the kernel itself laid out - it's a stock kernel.

Back near the beginning of the thread I had been building this ROM to be a test bed for overclock kernels, and so working with the stock kernel was necessary to build a baseline of performance.

I spent a lot of time tweaking and changing a lot of the little things that bring performance gains to the ROM to get it optimized so that when I got into kernel work I could squeeze the maximum amount of snappy performance from the device I could get.

Kernels are pending.

Leading up until the end of december, I had all the time in the world to work on this around the clock - which I did. I don't need nearly the amount of sleep most people do and routinely stay up for several days at a time, only to sleep for 3 or 4 hours and do it all over again.

Work picked up for me, and I gave pretty fair warning of several weeks to the effect this would happen. The time I spent working here around the clock was instead spent working for my bosses around the clock - 70-80 hour work weeks. During that time I was unable to continue any work on Android.

I started to get more free time over the last month again, to the tune of now I am putting in an average of 22 hours a day here working on S-OFF for current stuck S-ON people.

Today I took a break and spent some 9 hours building seperate flashable zip files for the majority of the stock apps. Bloater is not functioning properly and troubleshooting it right now is time not spent on cracking S-ON to S-OFF.

I am about to actually sleep, because I have day and night shifts stacked up starting in 16 hours, so I should be able to get another 9 hours of dev time in after I wake up. The next few days will be the first time i've spent more then a few hours not working on this issue and that is only due to work responsibilities.

I am uploading the flashable app packages now, and they should be ready to link to the forums later today - so people will be able to individually flash most of the stock apps through clockworkmod - I don't want people to have to do without the apps they paid good money for when they bought the phone, and everyone's idea of bloat is different. I try to give you all as much choice as possible to do what you want.

yogi2010 and I just spent...some 6 hours working together on extracting, reviewing and going over the new radio.img file together.

While this is going on, though, I am still uploading, sorting and making available a number of tutorials, guides and how-to's I have written to teach people how to develop things for this device. Browsing around the MT4GS forums some, you should turn up quite a few resources i've put together to assist developers in their projects so that they can spend less time looking things up and more time actually making them.

Bottom line is, while it may not seem like i'm getting much done, I am prioritizing my efforts to benefit the MT4GS community as a whole and not just the people running my ROM.

The S-ON to S-OFF issue is not an easy one to tackle, and while progress is being made it is the hardest thing to do because there aren't any guides, tutorials or any other information on how to accomplish this. In fact HTC is doing their best to PREVENT us from being able to do this, so it's taking all of the resources at our disposal to be able to make any progress, and where that fails we have to develop our own resources from scratch to get the job done.

I am building a custom hboot file that will hopefully help us get around the S-ON problem, but hex editing any file is no fun, hboot not being the easiest on to hit.

You may notice in the dev reference that we only have a small number of the over 30 partitions on this device figured out - the key to cracking S-ON is still (at least in part) hiding in one or more of the many partitions we have yet to map. This is a big focus of my time while i'm working on the S-ON issue - and that's more time with a hex editor crawling through partition dumps that I and others have made.

So yes, I fully intend to bring Bulletproof up to date with the current OTA. The HTC OTA they pushed over the air is broken - I found a leaked HTC signed copy of it as a full ROM which is now available here - but I just found that a few short days ago and we have not yet indexed and unraveled the whole thing.

Once that is done, I will be able to incorporate the changes into Bulletproof, but until then i'm not going to just slap something together and throw it out there - not my style. Making sure things are working well to me is more important then just getting it out there for my own dev work.

I also spent some time generating a bunch of test data that is published in a thread in general about the tv-out function of the device and all that goes with that, which ate up some time that could have been spent on this ROM.

I would have much rather been spending my time on playing with overclock and undervolt kernels, crawling through the kernel code i've found numerous things I want to change that have nothing to do with the CPU and am eager to implement.

All things considered - the S-ON issue I place at a higher level of importance then anything else we have going on and i'm literally giving everything i've got to making it happen. I figured out how to turn S-OFF devices back to S-ON a few days ago and now have both an S-ON and S-OFF device to test side by side on figuring out a way to hack HTC security and turn it off.

Please don't think that i've forgotten about or abandoned this ROM - there are just larger issues for all of us that need to be dealt with first. Meantime, hopefully everyone enjoys the options all those flashable app files I made today will give them. Over the next few days I will be uploading the rest of them as I get them knocked out which will include all the apps from the new update that I haven't already made available in flashable zips for people here.

I appreciate your patience, and hope this has helped answer your question - if not please let me know what you are still curious about and I will be happy to answer to the best of my ability - but for now I need to log out or it'll be another day sleep was optional vs. HTC S-OFF.