Dry spell

My apologies to the readers of this blog – the HoppeRx contributors have all be busy working on the next version of Windows Phone and posts have been few-and-far-between. Let me assure you that the next version is very cool and worth the wait. Thanks and please stay tuned.

1

Camera Preview orientation problems in WM6.5+

WM6.5 introduced some new layering/compositing technologies that have the potential to break some display driver assumptions. If your display driver is vulnerable to this problem, it will likely break in LTK test #4040 during camera preview orientation. If your display driver is not failing #4040, your driver is robust enough to accommodate the latest design…

0

Hopper log runtime mismatch

Establishing the correct value for Hopper runtimes can sometimes be challenging due to the number of places this value is stored. Some are reporting that the Hopper log runtime numbers at the top of the file don’t always match the values reported at the end of the file. Knowing which value to trust can save…

0

Relieving VM pressure from the GWES process slot

Windows Mobile displays are get larger and UI assets become more robust which is putting additional VM pressure on GWES to marshal all this additional data. Depending on the situation, implementing a “shared heap” using CeHeapCreate()to store assets may be valuable. The Heap will be relocated in the “mapper slots” thus reducing pressure on GWES…

0

Big Iron

The ability to try out bug fixes is a valuable part of the Hopper process and re-building images quickly is one of the easiest ways to improve your Hopper numbers. We recently went about trying to find the combination of build server parts that makes short work of our builds and wanted to share with…

1

Troubleshooting guide – part 2

Below is the second half of a well executed document from guestRx: Bulent Elmaci. Bulent has worked with Windows Mobile debugging for a long time and backs up his writing with a lot of experience. It is the first of a series of articles he has written to help our OEM’s become better debugging developers….

2

Troubleshooting guide – part 1

Below is a well executed document from guestRx: Bulent Elmaci. Bulent has worked with Windows Mobile debugging for a long time and backs up his writing with a lot of experience. It is the first of a series of articles he has written to help our OEM’s become better debugging developers, we will follow up with…

2

A Windows CE 6.0 Book that I keep paging back to…

I am not much of a programming book person, I am much more likely to select code and press “F1”. However, I find myself reaching for a CE 6.0 book and have been finding it quite useful. “Windows Embedded CE 6.0 Fundamentals” [Pavlov, Belevsky][ISBN 0735626251]  It is targeted as an “OS” book, so if you are…

0

Writeable code sections got you down? Fear no more!

Virtual Memory changes included in Windows Mobile 6.1 can relocate read-only code sections out of Slot 0 and into a higher address range. This change was taken to relieve pressure from our coveted, read-write Slot 0. This change will be transparent to most developers since code sections are by default, read-only and do not assume…

1