Has anyone else experienced OSupdate lockups on CE5 device once the udpate has begun. See the attached screen shot and text from case 1317959 that I have opened.
I think this can happen on any of our CE5 devices. I have created it on two different terminal types.
Airbeam OSupdate has about a 5 to 10 percent failure rate on MC9090 CE5 units. When doing an OSupdate of the Partition Table, Platform, Application, and OS, the OSupdate program will sometimes freeze after the partition download.
The symptoms are that the device will successfully download a partition like Platform, Application or OS, but then when it goes to install that partition, the status bar never moves and the device is frozen. It does not respond to pings, screen taps, or power button. The only way out is a cold boot, which is really bad, because now you have a device with mixed hex images and cannot continue any type of automated or RD update.
The package was built with Package Builder1.34, with the -n option. The –n option was thought to possibly resolve this issue previous, but it does not.
I also have the same issue on a custom MC70 with CE5.0. I will be testing on a MC3090 CE5 unit as well.
During development of the custom MC70, there was some work related to Fusion Radio interrupts, but it was not conclusive. This case requests that the true root cause for the OSupdate lockup be investigated.
I can email a screen shot of the frozen screen, and provide the OSupdate images. To help test, I have taken the V1.3 device zone images and added:
1. An Airbeam. reg file to set the package update.
2. Fusion profile.reg to get on the network
3. A calibration file so the device skips that
4. A copy file to start OSupdate on each boot.
I can mail the source for testing.
The Airbeam Package Builder used was 1.34, with V0.42 OSupdate.
In addition to the freeze, please also fix the location of the status bar to start on the left side instead of the middle.