Inconsistent booting

[manekineko]

Has anyone else seen this behavior? Anyone able to explain what causes it?

When I boot up it seems like there are 3 different possibilities:
1. Works fine, everyone is pleased
2. Boots up, but is extremely slow. Slowness is usually (but not always) permanent until next reboot. Will sit right after boot on partially rendered lock screen and be extremely unresponsive. Initial connection to network takes forever. Generally when you finally do manage to unlock, widgets take forever to load, and there is usually a message up about how the system isn't responding. Clicking the App button to bring up the app list will take 2 seconds or more to respond sometimes. Interestingly, running Neocore yields a benchmark half of what I usually get, at 9.5fps.
3. Boot dies almost immediately after launching haret, on the line "allocated dma buffer at ffc0b000, dma_addr 25260000". Words stop scrolling, though the cursor is still flashing, and a reset is necessary.

It strikes me as really weird that the boot can result in different outcomes. I would have thought it's pretty much deterministic, being a computer and all.

I haven't always had the 3rd outcome in there, but the first two have been with me pretty much since I started using XDAndroid I think, and I've restarted from a clean data.img with a reformatted SD card many times.

Edit: Also, just to clarify, I'm running with no overclock.

[bluedeer]

I have had these problems as well as others (spontaneous rebooting, especially if left idle for a period of time), though I haven't been able to narrow this down. I've even disabled the hardware 3d and reduced the overclocking by 100mhz and still no joy. I really want this project to be reliable and viable, but I wouldn't consider this 'stable' yet. Maybe there's hope with the nand flash, I suspect it has something to do with the way Haret accesses the sdcard and certain things in memory during boot time. Maybe Haret itself needs an update?

[steveholtam]

I get #1 and #2 quite a bit. After a rebuild, my phone is normally good for about a week before I start getting the above errors. Then it seems harder to get a good boot, like OP mentioned.

This is not a huge problem as there has been so much development lately that I am rebuilding my phone mostly before I see the above problems at this point.

It is something I'll research later if things slow down. Maybe I can figure out which file(s) are causing the hangs.

[InvincibleLiving]

I'm back to experiencing hanging boots when I try to load haret. The progress bar freezes just before the 2 vibrations and boot init screen.... only solution when it hangs is to soft reset.

Had this same issue about a month ago then it resolved itself just as randomly as it came.

[ndno]

One thing I noticed is that if I have been using WinMo for a while, I just "hard reset" (not restart), then power up and then launch haret.exe. Seems to always work (Android comes up and works smoothly) for me.

[arrrghhh]

Originally Posted by ndno

One thing I noticed is that if I have been using WinMo for a while, I just "hard reset" (not restart), then power up and then launch haret.exe. Seems to always work (Android comes up and works smoothly) for me.

What do you mean by hard reset? Gotta be careful with the terminology here...

Soft reset = pin under battery cover/pull batt

Hard reset = wiping device with power button/vol down... that whole mess.

[ndno]

Originally Posted by arrrghhh

What do you mean by hard reset? Gotta be careful with the terminology here...

Soft reset = pin under battery cover/pull batt

Hard reset = wiping device with power button/vol down... that whole mess.

Oops... sorry for the bad terminology. I meant "power down" not "restart".

[demonlordoftheround]

Originally Posted by arrrghhh

What do you mean by hard reset? Gotta be careful with the terminology here...

LOL! I thought that seemed a bit severe.