Stuck on Sashimi Status screen

[Farqui]

First of all I'd like to thank you for such a great tool, Sashimi is fab. However after using it for a few weeks now I have noticed some annoying behavior.

After initially installing Sashimi 8.0 the application started and worked through its various menu's flawlessly. However starting it now is a bit hit'n'miss as it often gets stuck at the initial "Sashimi Status" screen with the non-Sashimi "Phone" and "All People" soft keys shown. Occasionally the status screen will disappear but then no other Sashimi screen is shown, nor is Sashimi listed in the Task List, nor can I restart it (via the Sashimi icon within Programs).

I've browsed through these helpful threads and tried a few things which didn't help. So I yesterday I reinstalled Sashimi which then had the application working again Overnight the phone was reset, this morning I un-installed an app (WMLongLife), restarted and after launching Sashimi it's now sat on the initial Status screen again (it does appear in the Task List today)

Does anyone have any suggestions as to why this is happening ?

Device: HTC Touch HD
ROM: Duttys v4.1

Last Log entry;
08/12/09,08:24:03,SASHIMI 8.0 Initialized. Command line parameter: (none)
08/12/09,08:24:03,Security Policy 0000101a changed. Original Value: 1 New Value:1
08/12/09,08:24:03,Security Policy 00001001 changed. Original Value: 1 New Value:1
08/12/09,08:24:03,Security Policy 00001005 changed. Original Value: 222 New Value:222
08/12/09,08:24:03,Security Policy 00001017 changed. Original Value: 16 New Value:16
08/12/09,08:24:04,Settings file loaded. VALUE: \Storage Card\SASHIMI\Program\INI\settings.ini
08/12/09,08:24:05,Settings.ini entry added. VALUE: AlternateStorageLocation=
08/12/09,08:24:05,Settings file processed. VALUE: \Storage Card\SASHIMI\Program\INI\settings.ini
08/12/09,08:24:05,Custom Links INI file detected. VALUE: \Storage Card\SASHIMI\Program\INI\customlinks.ini
08/12/09,08:24:06,System Language Detected. VALUE:English-1033
08/12/09,08:24:06,Supported resolution detected. Value: 480x800x36864
08/12/09,08:24:06,Storage Card detected. VALUE: Storage Card
08/12/09,08:24:06,Alternate Storage Location. VALUE:
08/12/09,08:24:06,Idler script initiated. Idle timeouts will be prevented while SASHIMI is active.

[bengalih]

Hey Farqui,

I have not experienced the issues you describe really. Occasionally, when testing SASHIMI I either close and then relaunch it too quickly or somehow manage to open two copies and sometimes get occasional similar behavior - but I think this is usually due to the testing process.

I will say that SASHIMI shouldn't really be doing anything different when it loads one time as opposed to the other. 95%+ of weird issues like this are usually due to another application causing some sort of conflict. In addition, since most people only load SASHIMI once - when they first reflash their phone - these types of issues don't come up that much.

Even if it is a 3rd party program interfering, I would still like to assist in troubleshooting since I would like SASHIMI to remain as compatible and user-friendly as possible - but their are so many variables it is difficult to say where to look.

Normally - when running SASHIMI you should see two instances of Mortscript.exe running in TaskMgr. One should be about 255kb in size - this is the main SASHIMI program. The other is about 19kb is size - this is the wrapper "Idler" script that prevents the device from going into sleep mode by issuing wakeup commands every few seconds. You can actually kill the Idler script and probably not notice...but if you kill the other Mortscript instance, SASHIMI should terminate. Also, if you kill the main SASHIMI script, the Idler script should automatically terminate (when it realizes SASHIMI is gone) in about 10-15 seconds.
Depending how SASHIMI was launched, you will also see the SASHIMI.exe. This is really just another wrapper for launching and can also usually be killed without effecting the script.

If you look in the \bin directory you will see that there is SASHIMI.MSCR (194K) and SASHIMI.EXE (8.5K). Normally when you run SASHIMI via the shortcut it launches the .EXE file and you will see it in the TaskMgr as noted above. However you can directly run the MSCR file by clicking on it too. To be honest, the reason escapes me at this moment why I have set it up this way - but it was for good reason - I'll have to review the code to remember. I think however it was to allow SASHIMI to auto-register itself and MortScript if for some reason it became unregistered - or especially when running on a new device. However you may want to try just running SASHIMI from the .MSCR file and see if that works better.

Hopefully that information gives you some better insight into how it is launching and perhaps you can do some troubleshooting to see if any of the other apps may be interfering. Unforunately SASHIMI doesn't do extensive debug logging with the system (that's the nature of Mortscript) - but between the logs, the startup diags, and TaskMgr you should be able to do some decent checks.

good luck.

[Farqui]

Thanks for your comprehensive reply - really appreciated.

I'm using Sashimi quite a bit these days, in order to get it configured, but the hangs typically occur after a reset so running it twice isn't the problem.

TaskMgr hasn't worked on my device for a while and quick search on good ol'Google highlighted that the Process list fails to populated when G-Profile is running. I now see your Sashimi entry's and will see what happens when/if it next hangs.

I'll test out a few scenario's for a few days and report back...

Cheers, Farq's

[unpocoloco]

I'm having this problem too, and I've spent a LOT of time trying to pin it down. I think it might have something to do with customlinks.ini or deleteops.ini? I'm not sure. Can deleteops go into file10= ? Although, once broken, I seem to be unable to fix it, even if I delete the entire SASHIMI folder and uninstall/reinstall Sashimi 8.0. Something is stuck in the system. I've uninstalled and I'm reflashing without it right now, and maybe that will help. I hope so!

I was hoping to get a flawless install for my dad, who will be utterly confused if anything goes wrong with his touch diamond, and I'll have to give tech support anyway. This last step (to customize the shortcuts) has been really frustrating!

I'll check back if anyone finds more info. If so, I appreciate the help!

[unpocoloco]

That did indeed work

Although, after all that...the "Internet" tab that has a big picture of the world (normally launches Opera) does absolutely nothing with Groove ROM 4. ARGH! It never freaking ends with this phone. Even for a techie, this is a BIT much.

[bengalih]

It would really seem to me that the issues you are having are not with SASHIMI itself but rather other applications or registry changes you are installing WITH SASHIMI.

There is nothing in SASHIMI that is going to break ANY functionality in your phone because SASHIMI by itself doesn't do anything except install the things you tell it to install.

If you suspect there is a particular application that is conflicting we can attempt to find some sort of workaround...but I think you will be running around in circles until you start isolating your issue.

[unpocoloco]

Hmm, that's possible. I have gotten a consistent repro of geting the SASHIMI screen stuck on boot now. However if you process kill the MortScript.exe (both of them), then Sashimi opens successfully. I deleted SASHIMIAR.lnk from my startup, and things seem ok.

[bengalih]

So i take it you are using a ROM with SASHIMI cooked in? Thus your SASHIMIAR.lnk file?

Obviously that file should only run on startup (hence it being in the startup folder)...

What happens if you start SASHIMI manually after your phone has started up?

It is curious that you say you are killing two instances of MortScript and THEN SASHIMI opens successfully. If you look back to my description there should be ONLY TWO instances of Mortscript. If you are killing two instances and THEN SASHIMI is starting is it possible you have another application which utilizes Mortscript on startup???

[Farqui]

*update: I've found that Sashimi fails to get past the initial start-up screen if I have the G-Profile service running. As soon as I stop the G-Profile service then Sashimi completes it's start-up and operates normally.

Not sure if it's relevant, but I also then stop the G-Profile Quick Switch service too.

Btw, the G-Profile config application is still running in the background without adversely affecting Sashimi.

Hope this helps but it's confirms your suspicion that Sashimi isn't at fault, well not directly at least

Been a busy week with new ROM's seemingly all over the place

[professorman]

Okay. This one might have some substance to it. I went though my advance task manger's processess, and stopped a bunch of processes, and now Sashimi launches. I need to figure out which one is conflicting.