PDA

View Full Version : hanging issues with new builds


itje
30-06-2008, 10:16 PM
Hi
I have been trying to solve a problem im getting porting new builds, but I cant seem to get around it.
So I was hoping someone has experienced the same, and has solved it, and would be willing to share the sollution.

After flashing a new rom with a new build, it takes some time before the device responds to touching the screen. But for some weird reason, the cube works instantly, but if i try to touch startmeny or anything else on the screen, its "frozen" for some time, but after a little while, everything works flawless.
This also happens after a soft reset.

I have encountered this on several new builds :(

cheers

swtos
01-07-2008, 11:59 AM
I have the same issues. After playing with boot.rgu, random pauses are stopped...
We have to investigate this crap , more deeply ....
:)

itje
01-07-2008, 12:24 PM
yeah we sure do, I have the Herald and the Kaiser as well, and none of those devices have the same problem.

As you are pointing out, boot rgu can be a issue. Im leaning toward that its a problem with xip and some files in the new ported sys.
I have been trying several builds, with diffrent xip. But all get more or less the same problem.

It is really annoying, cause it really slows down the development of making better and faster roms. And I can say for my part, that it really kills the joy of cooking.

Here is what I have figured so far:
I have tried in.ex build 19949 and 20226.

I used "old" xip versions, like 19199, 19209, 19212 etc, some didnt boot, some did, but had hanging issue. I ported xip, to match buildnumber, and still had hanging issues.

I tried using the older builds, but with new xip. and...guess...no hanging issues...

So, as im sure you all know, its obviously related to the new builds, maybe its some files in shell folder (or other) that is not compatible with the oemxip?
Im hoping HTC will release the wm6.1 for our device soon, maybe a new original xip will help solve the problem?

But I have also been wondering if it can be related to the touch.dll? thats just a wild guess though :)