Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

And the survey says.......


YES!



It does work just like it should now! Pretty much any normal app will work like a non VZW Branded phone. I even think we could hit aGPS but I have not tested. I will ask you guys to do that.

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

YES!!!

Thank you, thank you, thank you kind sir!

Cant wait!

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

Thanks Scott! I'm really looking forward to the new rom bro!

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

Thank God. I thought I would have to chew my arm off.

-=+*SSK 1.5 Preview ROM*+=-
 

SSK 1.5 Preview ROM - Stable version is still 1.2!

This is a preview of the SSK 1.5 Kitchen. It is based on the E3 XIP from FormerPalmOS and the 21109 SYS files I used in 1.2. I remade the OEM folder from scratch. I used some drivers that were moduled in GC's kitchen as well as some of his HTC OEM's. Big thanks to GC for having a squared away stable kitchen!

I need everyone to test every GPS app they can think of that normally works on non VZW branded phones. I know that VZ Navigator stopped working. Im curious about aGPS. Report your findings if you know how to enable it using QPST. Please dont ask about it in the thread if you dont understand this portion of the post ;c)

I also used a slightly differnt manila engine this time because it was part of the entire theme I donwloaded. please tell me whatyour findings are with the changed engine.

The ROM is a little differrnt than my last ensembles. This has the HTC Keyboard but no large menu, large title or touchflo scrolling. It uses native windows scrolling which I think is much more precise. I left the HTC keyboard in because it can be a pain to find a cab.

Either way, please report anything you see; good or not so good. And remember, this isnt my day job ;c)

www.scottcrosler.com/TouchPro/beta/RUU_1_5_Preview_VZW.rar
www.scottcrosler.com/TouchPro/beta/RUU_1_5_Preview_SPRINT.rar



Edit: Also, I forgot to note that I put in the stock Opera and the stock JetCet printing app. Both were taken from stock VZW ROM. I also put in Google Maps and Live search installers freshly downloaded for your convienence ;c) Look in the my Documents folder for short cuts to installers.

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

bad news.... I dont know what changed, but my phone went back to not ignoring calls correctly again. I checked the registry key and the setting has not been changed. RejectIncoming or whatever it was. Still set to 1. But hitting ignore mutes the ring but allows it to stay connected.

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

I had to be the first one to say thanks ;)

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

Can someone try this out on the new beta?

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

Rather than quote multiple posts, here's my thought on UC vs. OEM and main memory vs. SD. UC anything that is designed to install to \program files, or that you may want to upgrade later, or that for some other reason doesn't work if not baked in. So yes, that means UC by default, bake only if you have to. Manilla has got to be the worst program ever in terms of the number of files it installs into \Windows...

BTW Scott - you should make it clear on your first page that your ROMs and kitchen support UC.

OEM always install to \windows. A .provxml can then later copy files to another directory but the originals are still baked into \windows. A cab will install to wherever it is told to in the .CAB. You can change this if you have a cab file editor but some programs may not like having their install directory changed.

Second, anything baked in is stored in IMGFS compressed. This means after it is found (the search time referred to earlier w.r.t. too many things in \Windows), it has to be decompressed then loaded to program memory. If installed after boot, it is not stored compressed so it should load faster.

Only exception to this is certain DLLs and EXEs. If you bake a frequently used application or driver into the ROM, then you can turn DLLs and EXEs into modules. They don't execute any faster, but they load faster since the OS does not have to find a virtual memory slot for them - their VM location is set prior to baking (that's what G'Reloc does - in case you were wondering). The faster load time is offset somewhat by decompression time. But you only get this benefit if the DLL or EXE is moduled in an OEM then baked in. Can't be done with a CAB. BTW - I believe Scott is doing this with many of the OEMs in his new release. Should be good!

Note - there is little to be gained from modularizing a DLL or EXE that is always resident. Turning something into a module only speeds up its load time - once it's loaded, it runs the same speed. But that load time is what makes the thing appear "laggy" sometimes.

Finally on SD vs. main memory, one advantage of SD is that you don't lose the installation when you re-flash, though you do lose any registry settings and the start menu links - unless you back those up. I expect main memory to be faster in terms of raw access (wider bus, no internal bridge or SD controller) but have not benchmarked it to be sure. Also, you can fine-tune the cache parameters and I/O parameters for SD(especially for SDHC) outside of the XIP - those parameters for the on-board flash must be cooked into the XIP and have to therefore be one size fits all.

FPOS

Re: -=+Feb 1+=- *SSK 1.4 Beta 4* +VZW and SPRINT+ - See OP! {CE OS 21109} Kitchen and
 

Just a min...