[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well, I took a look at the code again and the IdleTimerReset command is infact invoked prior to checking for storage card install and within the same subroutine used for non storage card installs.

What this means is that the

idle timer should be reset in between every file in auto mode

. So I don't know why you would see it working everywhere but the storage card installs.

The only thing I can think of is that the CAB you happen to be installing via the storage card is taking longer than the idle-timout duration on your device?

Can you recreate the issue? If so let me know exactly what is happening. Also, what your timeouts are set to and what CAB(s) you are installing at the time.

Again, the IdleTimeReset is run before

every

file in Auto mode. However it doesn't run during an install. So if the file is taking too long, I suppose it could go into idle state.

Also, are you sure your device is actually going into idle state? Idle state is the semi-off state of a device, and is not the same as just the backlight going off.

EDIT:

Ok, I just did some more testing and am finding it even harder to understand why this would be happening.

First thing I did was to remove the IdleTimerReset command entirely from SASHIMI.

I then set my backlight time out to 30 seconds and my Power-off (idle timeout) to 1 minute.

I let my device sit and made sure that after 30 seconds the backlight went out and after 1 minute the screen went off (device standby).

Then I ran SASHIMI in Auto mode with about 20 cabs in the \CAB directory. Since there was no manual interaction after initiating Auto phase I got the expected behavior, which is backlight off after 30 secs... standby after 1 minute.

I then moved all the CABs in the the \CAB\SC directory to do an Auto Storage Card install. During this run,

the device did not shut down the backlight or go into standby at all!

It would appear that the automated screen taps I have SASHIMI send are recognized like real taps to the device!

Therefore, I don't see how it is possible that the device can go into standby during Storage Card install mode at all. Unless, as previously stated it is taking more than 1 minute (or whatever your idle timeout is set to) to actually complete the install of a single CAB.

Anyway, if anyone performs tests to the contrary of this, or actually sees a problem with the behavior of SASHIMI please let me know. Also, be detailed in how to recreate the issue. Please keep in mind all the information presented here before jumping to any conclusions :)

thanks.

2nd EDIT:

Well, after thinking on this I still believe that all my above tests are valid and that the device can't possibly be going off during the auto storage card phase. However, it did bother me that if indeed a single cab did take longer than a device's idle timeout setting then the device would shut off and SASHIMI would pause until the device was taken out of standby. To fix this I have come up with a different method to reset the idle timer. Instead of resetting it within the script, I have SASHIMI calling another small script which will continue to reset the timer while SASHIMI is running. This way, the timer can be reset by the 2nd script even while SASHIMI is waiting for a cab install to finish. This should be a carpet over the whole idle timer issue and shouldn't need to be revisited again. Look for the change in the official release.