Vogue WM6.1 build 20924 kitchen

[nemanracing]

Originally Posted by drellisdee

I'm on VZW and and getting an internet failure with this kitchen. I've also tried everything I know to do as I've written several guides on converting data from another carrier to VZW including rewriting my dmu keys and am sure I covered all the bases. I'm thinking some files were left out. I'm getting cannot connect with current settings and all my settings are 100% correct.

Same here...

[boggsie]

Thanks for the update ...

No issues, whatsoever ...

Updater retrieved and applied updates without issue.
ROM built with all of my settings without issue.
Google Maps, Live Search, Windows Live, ActiveSync (Exchange Server), Bluetooth all working without issues.

The only change that I can immediately recognize are:
20924 seems a bit quicker (placebo ?)
PagePool Size no longer supports (check-box) for Dynamic Pagepool - any thoughts on why this went away?
Still cannot get pre-calibration of stylus to work with an OEM. (no matter how many times I re-create the OEM with post-calibration settings) - I'll probably move this to a post-flash cab install via provxml.

Again, thanks for the update ...

Best regards,
-boggsie

I also get the provisioning error. However, my internet still works. When I try to manually start provisioning it errors out with the 1012 error. The wierd thing is that I can browse with internet explorer and google maps works but pocket weather cannot download my weather information. I'll keep looking into it and post if I find anything useful. This is a great build thats for the awsome release....

[eme82]

gguruusa or anyone else that knows the answer...I have a small bug that has always somewhat bothered me with PPCKitchen Builds. When I press the start menu, there is a flicker of a white bar then the start menu appears. Using the same OEM's in another build I don't have this issue. I would stick with the other build but PPCKitchen always seems to be a cleaner build.

Let me know.

[boggsie]

Originally Posted by eme82

gguruusa or anyone else that knows the answer...I have a small bug that has always somewhat bothered me with PPCKitchen Builds. When I press the start menu, there is a flicker of a white bar then the start menu appears. Using the same OEM's in another build I don't have this issue. I would stick with the other build but PPCKitchen always seems to be a cleaner build.

Let me know.

Are you using QuickMenu or any other type of shell or UI enhancement?

I think I understand the behavior that you are describing. In my case, if I click directly on top of the windows icon (far upper left), then I don't see the flash, but if I click on the word Start, then I get the flash.

I use QuickMenu and I have always observed this behavior ... I believe it is triggered based on where you click, rather than on a build issue.

Please reply with your experience after trying this and let me know if you notice a difference.

Best regards,
-boggsie

Originally Posted by boggsie

Are you using QuickMenu or any other type of shell or UI enhancement?

I think I understand the behavior that you are describing. In my case, if I click directly on top of the windows icon (far upper left), then I don't see the flash, but if I click on the word Start, then I get the flash.

I use QuickMenu and I have always observed this behavior ... I believe it is triggered based on where you click, rather than on a build issue.

Please reply with your experience after trying this and let me know if you notice a difference.

Best regards,
-boggsie

I get the same white flash. I don't use quickmenus. I noticed this the other day with all the 207xx builds. I didn't notice it in builds prior to that. I am not sure what it is but it has no adverse effects on anything besides maybe being a little annoying. I use the same oems in all my builds and this only happens in the last 3 kitchen releases. Strange........ Also for me it has nothing to do with where I touch it is there regardless. On a wierder note it also happens on my titan with the same build and oems. However when you tap the start menu to open it no white flash but as soon as you tap an icon and the menu closes I get the white flash.....

Originally Posted by boggsie

Are you using QuickMenu or any other type of shell or UI enhancement?

I think I understand the behavior that you are describing. In my case, if I click directly on top of the windows icon (far upper left), then I don't see the flash, but if I click on the word Start, then I get the flash.

I use QuickMenu and I have always observed this behavior ... I believe it is triggered based on where you click, rather than on a build issue.

Please reply with your experience after trying this and let me know if you notice a difference.

Best regards,
-boggsie

I have also seen this behavior, however it seems no matter where I click on the start area it still does the same thing. I have noticed this since 20748. I 'm using the Opal enlarge start menu.
I also believe this build is quicker, and the text messaging issue is gone.
However, I can't get activesync to stop running in the background since 20748 using the different 'tweaks' I've always used using the task manager, and even adding the server seource and changing the schedule in activesync.
Anyone have the same problem?
Thanks for the update, though, nice build!
Ariel

[gguruusa]

Originally Posted by boggsie

Thanks for the update ...

No issues, whatsoever ...

Updater retrieved and applied updates without issue.
ROM built with all of my settings without issue.
Google Maps, Live Search, Windows Live, ActiveSync (Exchange Server), Bluetooth all working without issues.

Excellent! I hear including cambridge BT causes reboot failure.

The only change that I can immediately recognize are:
20924 seems a bit quicker (placebo ?)

that's the rumor

PagePool Size no longer supports (check-box) for Dynamic Pagepool - any thoughts on why this went away?

because it doesn't apply to apache/titan/vogue kernels.

Still cannot get pre-calibration of stylus to work with an OEM. (no matter how many times I re-create the OEM with post-calibration settings) - I'll probably move this to a post-flash cab install via provxml.

are you doing this by rgu or by prov in your build?

[savior02]

i found a bug! when u go to your inbox and you click menu and click select messages it doesnt work!!! what a pity! it worked perfectly on build 20755! anyone else have this problem? i reflashed several times still have the bug..

[boggsie]

re: pre-stylus calibration

In order to keep from getting confused, I have separated many of my personal oem's. One of them is myStylysCalibration and I have tried to get it to stick with both

an rgu [ffffffff-554a-4777-ab3d-fc1dbcdd2e4f.rgu]

REGEDIT4
;Stylus Calibration
;=============================================================
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
  "CalibrationData"="2000,1987 3147,3032 3129,929 861,961 878,3041"
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus]
  "Group"=dword:00000001
;--------------------------------------------

and provxml [mxipupdate_zzzz_myStylusCalibration_100.provxml]

<?xml version="1.0" encoding="utf-8"?>
<wap-provisioningdoc>
  <!-- *** COMMENTO *** -->
  <characteristic type="Registry">
    <characteristic type="HKLM\HARDWARE\DEVICEMAP\TOUCH" translation="filesystem">
      <parm name="CalibrationData" datatype="string" value="2000,1987 3147,3032 3129,929 861,961 878,3041" />
    </characteristic>
    <characteristic type="HKLM\ControlPanel\Stylus" translation="filesystem">
      <parm name="Group" datatype="integer" value="1" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

Initially, I thought it had something to do with my unit being a refurb replacement, but then in the 20755 thread, another user mentioned what could be described as stylus calibration issues, so I thought I would mention it in the event that I might not be doing something quite right.

Again, it isn't a big issue ... and it is easily resolved in about five seconds

Just to confirm ... this is by and large the best PPCKitchen upgrade experience I have had. After the updater downloaded and applied updates (without issue - yea) I build my rom with 20924 and haven't had one issue that was introduced by the update. Congrats and thanks!

Best regards,
-boggsie