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

[TwoDawgs]

Originally Posted by IsmaelPR1

One thing I noticed in all ROMs is that ActiveSync always turns on by itself, it doesn't run but it's always on in the background, how can I make that stop? If it's possible.

Originally Posted by phattooth

Dont think it is possible, but since i use it to check my exchange account i havent ever wanted it to stop!

I remember with WM 5.0 A/S would turn on automatically if Time Sync was enabled. This was back before I had an exchange server set up so I would turn off time sync to save battery.

Go to Start-Settings-Phone-Services-Time Synchronization and see if "Time Synchronize with mobile network automatically" is checked. If it is uncheck it and see if that helps!

[RONMAC]

Originally Posted by TwoDawgs

It may have something to do with the 6.5 beta I was trying. I switched back to SSK 1.2 and afterward performed a hard reset (center d-pad + reset hole). When I went to go use gps it would not work. I tried numerous times and finally re-apply the GPS fix from Bored. After applying the fix the GPS locked within seconds.

I will try another hard reset (center + reset) and see what happens and let you know.

Jim

I have bounced back and forth between a few ROMs including the 6.5 beta with multiple hard resets in between and I have not had to re-apply the gps fix.

Did you ever have VZNAV 3.0 on your TP?

[b0bzuruncle]

Do you have a link to the latest version?

You are right about "funky-ness"

I guess what I want to ultimately do is be able to configure the phone the exact way I want and then store away that image

If I bork something, I can update the ROM back to the way it was

Originally Posted by phattooth

To be honest with you, i always get "funky-ness" when i restore with sprite... i have just gone to using SDconfig. that works like a champ for doing all the installs i need after a fresh flash. you should really look into, once you use it, you'll wonder why you never did before, i promise you that!

[RONMAC]

Originally Posted by phattooth

http://forum.ppcgeeks.com/forumdisplay.php?f=75

you should also check http://forum.xda-developers.com/ as well... they have tons o schtuff.


EDIT: step by step though buddy... worry about the themes after you get a handle on the kitchen. i promise, one go in the kitchen will not be your last flash!

Ain't that the truth.

Have flashed every ROM from Scott and have been going through serious withdrawal since he has been on vacation

[phattooth]

Originally Posted by b0bzuruncle

Do you have a link to the latest version?

You are right about "funky-ness"

I guess what I want to ultimately do is be able to configure the phone the exact way I want and then store away that image

If I bork something, I can update the ROM back to the way it was

Cant help ya much with the sprite or back up stuff.... i just dont use it anymore.

One thing i can suggest though, is dont back up your mail... that is always where i had the most issues with sprite.
I would suggest you check out whether IMAP is an option on your mail server, and back up everything but mail when you use sprite....

sorry man, but i'm not sure what you are looking for exists in the WinMo world. You're gonna find that some things/habits/practices you do in PC land dont have an equivalent on WM. sorry, but true.

[b0bzuruncle]

Do you have a link to the latest version? of SDBuilder?

Thanks

[bast525]

Originally Posted by FormerPalmOS

I have that - dumped the XIP and have all the modules ready to play with. Just need to figure out what hardware is different between diamond and touch pro that affects early boot phase. But I'm reasonably confident that DDI can be switched. Stay tuned - hopefully I will have progress this weekend.

I can't put in the mad hours Scott puts in on these things.

FormerPalm - Okay, here's what transpired last night (love that word... transpired...). Da_G asked me to post the os.nb.payload from Scott's kitchen, which I did, and then he took out the existing ddi.dll, and packaged in the ddi.dll from the 2.03 Diamond rom (I was wrong when I said 2.09, 2.03 is the new one). He posted that back up, I put it in my ROM folder in the SSK, and cooked it up. Flashed the rom, I get the VZW screen with ROM/Radio versions, then a black screen... and nothing else.

The good news there... is that I guess the other methods I was using to try to insert this ddi were working, becuase I was getting the exact same result There was another post in Da G's thread where someone posted a zip with the ddi.dll and a host of other dll's which he stated were "Required files for this DLL" that he extracted from Da_G's rom. Something like 12-15 dll's in that folder, all video related. Anyways, I tried overwriting my existing system files using those files with Total Commander.... same result as listed above.... So yeah... I'm confused, considering that rom is for an AT&T fuze, I didn't expect there to be any differences in video hardware, but then again, they are on a different CPU than we are, and the video is incorporated into that, no?

I won't give up though... this is like... my life's mission at this point

[phattooth]

Originally Posted by b0bzuruncle

Do you have a link to the latest version? of SDBuilder?

Thanks

SDconfig or BuildOS?

[bast525]

About Sprite backup having 'funkiness'... I've had really good luck with SPB Backup, but more recently, I've switched to using the backup and restore features built into SK Tools. It's not as pretty as SPB, but seems to work better. Plus, you don't have to buy the full version of SK Tools to use it. Just download the trial version, on which many things ARE limited, but the backup/restore feature is fully enabled!

The ONLY problem I have with this method, and I haven't looked too far into because it hasn't bothered me, is it does not back up messages. When I restore a backup, my SMS's are gone, and I have to re-set up my email account, which immediately re-pulls down any recent emails, so no harm done, just a extra seconds.

Other than that, all my apps and settings are restored perfectly, and it's like no hard reset was ever done

[FormerPalmOS]

Originally Posted by bast525

FormerPalm - Okay, here's what transpired last night (love that word... transpired...). Da_G asked me to post the os.nb.payload from Scott's kitchen, which I did, and then he took out the existing ddi.dll, and packaged in the ddi.dll from the 2.03 Diamond rom (I was wrong when I said 2.09, 2.03 is the new one). He posted that back up, I put it in my ROM folder in the SSK, and cooked it up. Flashed the rom, I get the VZW screen with ROM/Radio versions, then a black screen... and nothing else.

The good news there... is that I guess the other methods I was using to try to insert this ddi were working, becuase I was getting the exact same result There was another post in Da G's thread where someone posted a zip with the ddi.dll and a host of other dll's which he stated were "Required files for this DLL" that he extracted from Da_G's rom. Something like 12-15 dll's in that folder, all video related. Anyways, I tried overwriting my existing system files using those files with Total Commander.... same result as listed above.... So yeah... I'm confused, considering that rom is for an AT&T fuze, I didn't expect there to be any differences in video hardware, but then again, they are on a different CPU than we are, and the video is incorporated into that, no?

I won't give up though... this is like... my life's mission at this point

Well, Da_G knows what he's doing on the XIP so this reduces my confidence that anything I might do differently will work.

DDI.DLL is the 2D driver - think of it like trying to load an ATI driver for your NVidia graphics card - it's definitely hardware dependent. AT&T Fuze is a GSM device. I don't expect the graphics hardware to be different but it could be. But let's assume it is the same.

DDI is called by GWES.DLL (Graphics, Windowing and Event Subsystem). If GWES isn't calling it correctly your system will hang after early boot trying to load the late boot OS. There shouldn't be any other dependencies though. However it may also be called by d3dm...