[Windows Mobile Software Development] meltwater:
Hopefully a cab will come. You can have a go at installing it manually. The only tricky part is editing your tab control file [26948339_manila], but you can post that on the thread if you are not sure about that. Just keep your original and you can restore it if you get problems.

EDIT: Which rom was it? Interesting to know when it gets cooked (I can also keep an eye on the rom thread for issues related to the tab - more testing = more fixes = better result). I only know about Zard's Rom so far.

_________________________________________________________

News on the sense stability testing:

It is on going...the problem I am getting is that I get different results each time. The options for debugging sense is very limited so it is a difficult task.

As far as I can tell the main stability problem occurs when sense is loading for the first time (i.e. generated a new manilafull.xml file), if it is left to load (I think it continues even after the home tab is up) it sometimes freezes sense. As far as I can tell, this doesn't occur everytime or if the tab is selected early on (so maybe it internally initialises it or perhaps interrupts the initial loading maybe or loads something which is needed in a different order). Once this initial stage has passed though, I haven't had lock ups, and there is every chance that this problem isn't the tab at all - I do have a mix of CHT versions (including dev ones) so it could be that, I did have issues at around the time I was messing with CHT (further tests are needed). Not knocking CHT by the way, love it and it is probably down to not cleaning my system each time.

At the moment I've rolled it back to ChangeSet 3495 but I may need to go back further.

The test I am running is:

Delete manilafull.xml.

Softreset to force sense to re-load fresh

Wait for everything to load and then monitor for the clock to freeze (at least 10 min).

The problem is, each time I think it is ok add a newer file (even with the slightest change) and it fails, rollback to the previous one and that starts to fail...

It would be handy if you guys and run some similar tests, perhaps by switching your versions of your tab control file [26948339_manila] between one with the tab and one without (don't forget to remove the HKLM\software\htc\manila\configuration keys). At least that way I can confirm that there is some issue located in the tab, even if my device has other problems (I expect it as I hack it hard)!

If there is something which isn't 100% then it would be good to iron it out now, even if it is just an initial start up problem.

UPDATE:

OK, I admit defeat, I've removed the tab and did the same test and get the same freeze. Answer is...

1-In my case I have a another problem with sense (but I can live with it, 1st startup only sometimes)

2-I can't test if there is an issue or not caused by the tab (but at the moment I don't think there is)

3-I will still watch out for any non-startup related issues and obviously anything which just kills it, but will have to rely on you guys to report if there is a specific issue.

Note: I have to repeat the test about 3-4 times sometimes to see a problem, it may be worse when connected via active sync, I'm just not sure any more.

I'll save this wild-goose chase for when I re-flash to a clean rom (will be a while) and I can test the system stability before adding the tab. Overall, I still expect the tab to become less likely to cause issues as more of the unused stuff is removed since the more it becomes a dumb display the less it does internally, but the unused stuff is proved by the fbtab to be reasonably ok so baring things which kill it totally I think it is ok. Normally nothing should be running in the background for the tab so that should rule out most issues with sense once it has loaded the 1st time.

Well I've convinced myself now its ok, please let me know if there is a major difference with and without the tab installed. Particularly between builds.

______________________________________________

@winderp, will look at gb2312 now! :D

1st try will be to test to see if I can do it the way I've started doing it, then if no luck with that will look into the other methods.

[see attached exe - should generate a temp file [called tempfile.xml] which as the encoding corrected, and then loads that instead. If it works should be able to do it without the temp file, but might be useful for test.]

@Captain_Throwback

Yep just had the same thing on the same item twice, looks like the problem is within the sense code detecting what was hit. Will see if I can fix this, may need to put in the static header like we talked about.