+Feb 5+ *SSK 1.2 Stable* {CE OS 21109} Kitchen and ROM

[scrosler]

Originally Posted by FormerPalmOS

Scott,

Also, on the phone settings issue, I now believe this could be something that's changed in your carrier pack or OEM Apps pack since the VZN3 days. Why do I say this? I tried XIP 20754 (straight outta the most recent Diamond ROM) plus SYS 20754 but the phone settings problem persists. The only other place I can think of to look is whatever OEM pack contains the file PhoneSettingExt.dll - see if something in a .provxml or .rgu changed from the VZN3 carrier pack to your latest kitchen. Other place to look is whatever pack contains the HTC Phone application (creates registry settings under HKLM\Software\HTC\Phone).

Ok, I just ported to 20754 SYS with matching XIP... SAME OEM PACK.... No phone settings problem.... NONE.....

The problem only exist with your rev2.

It has nothing to do with my OEM files at all. Could your mappings be off in the XIP or maybe you packaged the OEM/DLL file and I left them as DLL's?

Im going to swap entirely to your Rev2 XIP now.... Everything is working as it shoudl on 20754 build. Now if it breaks after swapping XIP's then we just need to find the disconnect. I can send you my current kitchen and you can shoot me yours.

[FormerPalmOS]

Originally Posted by scrosler

Until I can figure out exactly what causes the phone settings I will stay with ver 1E. I did an EVEN XIP swap and the phone problem persisted where as the 1E didint. I will try it with a fresh VZW split but..... I think its more than just what you think. Its not the OEM files as I had made no changes. Even between releases. This is the first release where I moduled all OEM apps and drivers. I dont beleive the issues is int he OEM. Its a compatibilty issue we have not discerend yet.

I know you say the page pool is not changeable but i have hundreds of users that will tell you otherwise. The page pool changes as it set. Look at the ROM and see. Look at 2.1 and see. I know you say you cant change the page pool but it changes. It reflects the change in all aspects. IM sure of this.

Secondly, when I put out version 1.2 with the 1E sys I turnded the default encryption to off. Remember me posting in your thread how to do it? Encryption is off on this as well but accessible. I know how to mod a boot.rgu man, give me some credit here.

EDIT 0: Do you have a fresh VZW OEM folder? If not I can post one if you need it for testing.

EDIT 1: Porting to 20754 now....

EDIT 2: If you want this current OEM pack for testing let me know. Not releasing the kitchen just yet....

EDIT 3: I upadted ALL phone related DLL and packages in the new OEM pack. That includes PhoneSettingExt.dll

EDIT 4: Just got first boot with 20754.

Here's XIP ver 3 based on 20754. PP at 12 but the changer app works. No changes to dll start or base addresses so no need to change header files relative to ver 2. However, you need to double check your SYS .RM and .VM locations - be sure you are using the right addresses for ver 1 or ver 2.

BTW - if you change boot.rgu and want it to affect anything at early boot, you have to turn it into a .hv, cook it into the XIP, re-build the XIP and implant it into os.nb.payload. But for changing encryption default, it works without all of that because the SDMemory profile isn't loaded during early boot.

I'm cooking right now with this XIP, 20754 SYS and the OEM pack from kitchen 1.2. Will report how it goes...

[FormerPalmOS]

Originally Posted by scrosler

Ok, I just ported to 20754 SYS with matching XIP... SAME OEM PACK.... No phone settings problem.... NONE.....

The problem only exist with your rev2.

It has nothing to do with my OEM files at all. Could your mappings be off in the XIP or maybe you packaged the OEM/DLL file and I left them as DLL's?

Im going to swap entirely to your Rev2 XIP now.... Everything is working as it shoudl on 20754 build. Now if it breaks after swapping XIP's then we just need to find the disconnect. I can send you my current kitchen and you can shoot me yours.

Sweet - narrowing in on it. YOu said with matching XIP - what XIP? Mine or the one from the Diamond ROM? That one shouldn't boot. If you have an officially-released CDMA Touch Pro ROM with 20754, please share!!!

[scrosler]

Originally Posted by FormerPalmOS

Sweet - narrowing in on it. YOu said with matching XIP - what XIP? Mine or the one from the Diamond ROM? That one shouldn't boot. If you have an officially-released CDMA Touch Pro ROM with 20754, please share!!!

Whaqt one shouldnt boot?
I have my own set of XIP's. Yes, I have a perfect working ROM that boots the SYS files and all functions with 20754 and matching XIP. Its nice ;c)

What exactly are you looking for?



step 2: Right now, I am going back to 21109 with this current 20754 XIP.
step 3: Then 21109 with your REV 2.

I have proven its not the OEM pack.


EDIT: the build I am using from Diamond ROM is 20764, not 20754. CAn you confirm what you have as well? Screenshot attached

[FormerPalmOS]

Originally Posted by scrosler

Whaqt one shouldnt boot?
I have my own set of XIP's. Yes, I have a perfect working ROM that boots the SYS files and all functions with 20764 and matching XIP. Its nice ;c)

What exactly are you looking for?



step 2: Right now, I am going back to 21109 with this current 20764 XIP.

step 3: Then 21109 with your REV 2.

I have proven its not the OEM pack.


EDIT: the build I am using from Diamond ROM is 20764, not 20754. CAn you confirm what you have as well?

An un-modified XIP straight from a Diamond ROM shouldn't boot. At minimum the OEMXIP files from the same device must be used.

Yes - what I have is 20764 - typo.

If you have a kitchen with 20764 sys, 20764 XIP and it is working with no phone settings issues, can I get that? Definitely something strange with what I've just built - still have the phone settings issue and long end key doesn't work.

If you have a good no problems base, I'd rather start there and re-implement the changes that got us more memory and more speed - rather than trying to debug what I have now that ain't working.

[scrosler]

Originally Posted by FormerPalmOS

An un-modified XIP straight from a Diamond ROM shouldn't boot. At minimum the OEMXIP files from the same device must be used.

Yes - what I have is 20764 - typo.

If you have a kitchen with 20764 sys, 20764 XIP and it is working with no phone settings issues, can I get that? Definitely something strange with what I've just built - still have the phone settings issue and long end key doesn't work.

If you have a good no problems base, I'd rather start there and re-implement the changes that got us more memory and more speed - rather than trying to debug what I have now that ain't working.

Agreed! Do you know how many times I just say screw it all, split the stock ROM and start over? Ughhh....

Yeah, I will up the kit in a little bit. Its solid as ****! Did you see the screeney I put up. All functions work as they should.

But yes, its not the XIP from the split ROM. This XIP I have has already been worked and ready to roll ;c)

[phattooth]

Glad to see you guys are makin good head way!

I wish i could play today, but the wifey and I are gettin ready for a house full of Super Bowl fans!


See you all tomorrow.... sorry i cant help today Scott.



GO CARDS!!!

[ka911]

well done Scott on b4 release.

[scrosler]

Originally Posted by ka911

well done Scott on b4 release.

You like it?

[FormerPalmOS]

Originally Posted by scrosler

Agreed! Do you know how many times I just say screw it all, split the stock ROM and start over? Ughhh....

Yeah, I will up the kit in a little bit. Its solid as ****! Did you see the screeney I put up. All functions work as they should.

But yes, its not the XIP from the split ROM. This XIP I have has already been worked and ready to roll ;c)

Where did the XIP come from? I'm going to try XIP ver 1 with what I just built - see what happens.