Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

Not sure if there is a cab anywhere for the stock Verizon Manila or not... i personally thought it looked like @ss and havent ever looked back.

The close ok are from a WinMo 6.5 BETA that has been released.


If you dont like these things, you can change both of them in more if you built your own ROM in the kitchen!
The Stock VZW Manila is even available via the kitchen.

Re: weather issue w/ SSK 1.5M OS Kitchen and OS 21109 ROM
 

That my friend is MUCH better!
An explanation like that gives us much more info to work with!

OK, so what you're seeing is TF3D definitely crashing on you... that's why it goes through "TF3D is starting up" phase, and boots you off the weather tab.


OK, 2 more questions.

-1 which manila did you choose in the kitchen when you cooked your ROM?
-2 like kazi asked last night... did you do a hard reset immediately after you flashed?

It has been discovered that if you dont do a Hard Reset after first boot that you may end up with unexplained goofiness like you are seeing now.


To do a Hard Reset, on a Verizon phone, do the following.
-Hold down the center D-Pad while pressing the soft reset hole.
-Keep the center D-Pad held down until you see the gray screen with onscreen instructions.

NOTE: Hard resetting will erase all of your personal settings and any customizations you have done so far... normally i would recommend you back up here... however in your case, backing up may only back up your weather tab issue.


Hope that was helpful.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

I'm having issues with C2 version of kitchen, I'm going back to Rev B with 21015... My alarm didn't go off this morning, and as it turns out... my phone was frozen! this is about the 4th lockup since Rev C2...

luckily I took off work today so it all worked out...

I don't think that Scott, whats the difference between C2 and B??

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen incl WM6.5 Build 21159 and OS 21015 ROM
 

*EDIT* Grrrr, I quoted the wrong post like 4 pages back.

Ted, the only problem you had with your sdconfig was re-installing apps that were cooked in? I've made sure not to duplicate and have not had a problem with UC at all. I'm rolling back to 20931 in about 15 minutes. I might need a bit of help with trackme when I get there.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

Did you have S2U2 engaged over night... i mean before the alarm went off, was S2U2 on?

I have had S2U2 funk with my alarms before.

Also, what are you using for an alarm app?

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

I use regular windows mobile alarm... i also use Pocketshield over S2U2... i think unlocking in up to down motion is much more natural then left to right...

I usually hold the phone on my left hand...

anyway, are there better alarms? that i should know about?

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

good luck, pm me if its better b with 21015, i cooked this same combo...
alarm didnt go off either...maybe its the 21015 sys...

c2 with 21015 freezes up
b with 21015 freeze up no alarm wake up

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

I had the same thing happen with mine this morning also. Flashed to 21015 with c2 and no alarm this morning. Thank goodness (or maybe not :) ) the wife had her alarm set also, just using windows mobile alarm will try g-alarm and see if that works.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -
 

Here is something interesting... a bit OT but still interesting. I was snowboarding yesterday, and hesitantly took my phone with me. About half-way through the day, I got sneaky and started checking the forum. I noticed a mark on the LCD that could only be compared to a cigarette burn. I nearly puked, thinking I had damaged the LCD. I intended to hit Scott up, since I think it was him who dismantled the thing so I could find replacement parts instead of flashing it back to stock. This morning I saw that the mark is gone!!!

This leads the the actual question: Has anyone else experienced anything similar? It could be an issue with it being cold, but it was in my pant pocket, and my leg should have kept it warm enough.