WM 6.5 Kitchen QVGA and VGA Developer Edition - Page 565

**joojoobee666** · #**5641** (**permalink**) 06-30-2009, 06:46 PM

Quote:

Originally Posted by qball1616

joojoobee666,

i took the xip.bin from the \temp folder....i am assuming that is the new xip.bin that the kitchen created when cooking....correct me if i am wrong and/or looked in the wrong spot

No, that is right.

qball1616 · #**5642** (**permalink**) 06-30-2009, 07:22 PM

Quote:

Originally Posted by joojoobee666

No, that is right.

so do you think that the kitchen is building the xip.bin wrong?

**electronicrice** · #**5643** (**permalink**) 06-30-2009, 07:41 PM

joojoobee, your link for 192 dpi files is broken

**joojoobee666** · #**5644** (**permalink**) 06-30-2009, 07:48 PM

Quote:

Originally Posted by electronicrice

joojoobee, your link for 192 dpi files is broken

Thanks, fixed. Sometimes Firefox does some weird things when editing a post.

**joojoobee666** · #**5645** (**permalink**) 06-30-2009, 07:53 PM

Quote:

Originally Posted by qball1616

so do you think that the kitchen is building the xip.bin wrong?

Well, I'm not sure. I guess I was just trying to make sure it WAS ok. Easiest way to tell is to dump an known working XIP and compare the maps. Make sure that things look pretty much the same. So far as I can tell, the SYS files you are using are not causing the issue. So that leaves the XIP as a possibility. The only other possibilities are Carrier files, OEMDrivers and the likes. Seeing as I don't own one, I can only help you troubleshoot with what I know.

Can you post a known good xip and the one your kitchen created?

qball1616 · #**5646** (**permalink**) 06-30-2009, 08:27 PM

Quote:

Originally Posted by joojoobee666

Well, I'm not sure. I guess I was just trying to make sure it WAS ok. Easiest way to tell is to dump an known working XIP and compare the maps. Make sure that things look pretty much the same. So far as I can tell, the SYS files you are using are not causing the issue. So that leaves the XIP as a possibility. The only other possibilities are Carrier files, OEMDrivers and the likes. Seeing as I don't own one, I can only help you troubleshoot with what I know.

Can you post a known good xip and the one your kitchen created?

I am using an older version of bepe's kitchen. Where would i find the xip.bin?

would it be the out.bin? I am guessing that I would just change the name to xip.bin?

**joojoobee666** · #**5647** (**permalink**) 06-30-2009, 08:48 PM

Quote:

Originally Posted by qball1616

I am using an older version of bepe's kitchen. Where would i find the xip.bin?

would it be the out.bin? I am guessing that I would just change the name to xip.bin?

Old style? I don't know. I thought we agreed there was a copy under temp after a build? Unless you are referring to the old XIP?

**Lmiller1708** · #**5648** (**permalink**) 06-30-2009, 09:23 PM

I was just wondering if anyone else has had any issues with there phone turning off?
This just started happening to me with 21820.
I can't figure this out any help would be great!

I have a vogue, radio 3.42.30.

I have never had this issue before with any builds...

**Adrynalyne** · #**5649** (**permalink**) 06-30-2009, 09:35 PM

Quote:

Originally Posted by da_reeseboy

I normally have to recmod browsingcore as well...

Recmodding browsingcore breaks security for me, every time.

ai6908 · #**5650** (**permalink**) 06-30-2009, 09:49 PM

Quote:

Originally Posted by swampy395

don't know if this will help but I'v used the same 21202 dpi and 0409 files on every build since 21202 only changing "Common files" and not had any of the probs in recent posts no gray no browser probs no screen lock probs

swampy395

Would you mind sharing your dpi and lang files please!

Quote:

Originally Posted by qball1616

so do you think that the kitchen is building the xip.bin wrong?

Best way to find out if you have issues with SYS or XIP is to interchange them for known good one. You can easily do that with VK.