8 APR 09 - UPD 25: Mods please lock this thread!

[rainfreak]

Originally Posted by bmb2n

My S2A works fine with stock radio v1.0.3.15F. All I did was installing the S2A phonecanvas.

Maybe it does, I couldn't tell you. I am one who likes the newer, better product. So I installed the new radio almost immediately after it was released.

For the life of me I can't figure out why anyone wouldn't be running this new radio...

[RONMAC]

Originally Posted by rainfreak

LOL.

First, the easy stuff. I only keep .NET CF and stuff like that in the kitchen, everything else I do with the UC. UC lets me install about 15 apps, copy ringtones over from my sd card, replaces my S2U2 settings via a registry edit, etc. So for me, keep the kitchen simple.

As for the radio, the 1.11.00F version is what allows you to have the S2A capabilities. Don't ask me why, I don't work for HTC I just know that is the fact and I deal with it. There are other benfits of the new radio as well, including better overall performance and less of the "heat" issues that people comment about with their TPs.

You can flash the radio and you will not lose anything on your TP, it is not the same as flashing a rom and starting over. Though I did just notice that you are on VZW and the radio is a Sprint radio. I know that I have read that it still works, but I wanted to point that out before you do it, in case you have any problems.

So I have the stock VZW ROM and the stock radio. I loaded the S2A black w/curtain and it works like a charm. There is no need to upgrade the radio to take advantage of this CAB.

Please let me know if you need the cab as I have it available.

[RONMAC]

Originally Posted by rainfreak

Maybe it does, I couldn't tell you. I am one who likes the newer, better product. So I installed the new radio almost immediately after it was released.

For the life of me I can't figure out why anyone wouldn't be running this new radio...

I ran the new radio for a few weeks and really didn't notice any real difference in performance but I also live in NY so there are plenty of towers here for me to cling to. In would imagine that if you live in an area where coverage can be iffy, a different radio might help.

[zim2323]

Originally Posted by RONMAC

So I have the stock VZW ROM and the stock radio. I loaded the S2A black w/curtain and it works like a charm. There is no need to upgrade the radio to take advantage of this CAB.

Please let me know if you need the cab as I have it available.

I do have the CAB file also, but what is weird is that the S2A is not working, as I mentioned in a previous post. On first boot, it will come up but is not functional. After 3 seconds I get the traditional phone buttons.

Maybe enabling/installing S2U2 S2A breaks something with S2A.

I'd still really just like to get the curtain file only as a CAB.

[Kamokazi]

Originally Posted by rainfreak

Maybe it does, I couldn't tell you. I am one who likes the newer, better product. So I installed the new radio almost immediately after it was released.

For the life of me I can't figure out why anyone wouldn't be running this new radio...

Bob's extensive testing showed no battery life differences. This was way back in like the first SSK thread, or maybe even VZN 3.0.

I did not notice any differences in recption. And I live in an interesting area...in the sticks, but near an EV-DO tower. So there are lots of great signal areas and lots of bad, and even no serivce areas near me. I payed close attention and was getting the expected recption everywhere. However, this was just my observed performance, and was not even remotely scientific like Bob's battery tests, or my ghetto GPS test below.

What I did notice, and others including Scott noted, that GPS locks were quicker. After getting an initial fix with each radio, I soft resetted the phone and got a fix 5 times with each. The stock 1.03 radio averaged something like 8.2 or 8.3 seconds...the 1.11 radio was 11.0 average. This was all done on the same day within about an hour timeframe, outside, 20ft+ away from my house and no tall buildings or other interference nearby.

So really it's very minimal, but I am sticking with 1.03 for now. Like someone else said, your mileage will vary with radios, so you should test them out to see if there are any differences in your area.

EDIT: Also, I did use the S2A w/ curtain just fine on 1.03 radio...but I never OEMed it in. This was way back on a VZN ROM I think...

[oldman]

Originally Posted by zim2323

Back to this question...

Is it better to cook .Net 3.5 in the kitchen or install afterwards?

Also... Is .Net 2.0 default in WM6.1 now?

Net 3.5 is Microsoft's latest version. I think (but not sure) that it's standard in all the latest builds.

The original Verizon TP had 2.0 (they are always a day late and a dollar short). Don't know about the new ones they are selling today....Probably the same.....I think that when they eventually come out with a ROM update, they will put in the Net 3.5. I really haven't heard any rumors or stuff about an upgrade, I'm just assuming that they will eventually see the light and upgrade their ROM.

Bob

[RONMAC]

Originally Posted by zim2323

I do have the CAB file also, but what is weird is that the S2A is not working, as I mentioned in a previous post. On first boot, it will come up but is not functional. After 3 seconds I get the traditional phone buttons.

Maybe enabling/installing S2U2 S2A breaks something with S2A.

I'd still really just like to get the curtain file only as a CAB.

Not sure what is causing this issue for you.

I do not cook with S2U2 as it has changed yet again proving that cooking with some EOMs doesn't make sense as they can be updated frequently and will cause you to re-cook everytime.

Mysuggestion would be to recook without S2U2 but WITH the S2A (either black or white) and DL S2U2 1.52 and see if you can get them to play nice together.

Hope that helps.

[RONMAC]

Originally Posted by oldman

Net 3.5 is Microsoft's latest version. I think (but not sure) that it's standard in all the latest builds.

The original Verizon TP had 2.0 (they are always a day late and a dollar short). Don't know about the new ones they are selling today....Probably the same.....I think that when they eventually come out with a ROM update, they will put in the Net 3.5. I really haven't heard any rumors or stuff about an upgrade, I'm just assuming that they will eventually see the light and upgrade their ROM.

Bob

Maybe thats why we haven't heard from Scott. VZW hired him to create a ROM for the Touch Pro and he is hard at work right now making this the best damn $349 dollars ever spent for a phone!!!

[jmorton10]

Originally Posted by zim2323

Again, I still don't get what the radio has to do with the phonecanvas, dialer/curtain, or S2A.

I don't quite get that either.

I have tried at least 4 different radios in my TP & S2A worked just fine with any of them.

~John

[DigitalAttic]

Originally Posted by zim2323

Why would custom ROM's not have NCF2? My experience so far is that all of Scott's ROM's have NCF2 left in. Why would someone not want that cooked into the ROM?

Thanks!

Use the MS .Net Config. tool and check for yourself it's not there on most custom ROMs. In all the ROMs I've flashed with Scott's kitchen, NCF2 is stripped out and replaced w/NCF35, and that's why Scott has it checked by default.

I don't know what your "experience" entails to come to this conclusion. I have examined the SYS and OEM folders extensively, and have installed NCF2 habitually after a flash. NOT ONCE has it reported it has to "uninstall" a previous version of NCF2, and the utility that Bob posted, which I have used habitually shows NO NCF2 on a ROM after flash.

Why would someone not want NCF2 cooked in... simply because of "new is better" habit, which in this case it isn't completely valid, as most apps have been tested/developed using NCF2, which is why it's part of the stock ROM base build.

If you recall, Scott didn't develop the base kitchen on which SSK is based Eric Rice did, and he replaced NCF2 w/NCF35.

Anyway, that's my take on it, and I stand by my observations.

QED - DA