View Single Post
  #5 (permalink)  
Old 12-18-2010, 10:59 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.414; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by 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.
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.
There are too many factors at play to expect the same results on similar devices. Also, even with buffered ECC memory, computers don't always perform the exact same.

A couple of things to note as far as performance goes, I highly recommend staying away from class 10 and class 6 cards for this project. Class 4 is where I would go for, and here's why.

Flash memory has to be optimized for specific functions. The higher class cards are rated for high throughput but generally suck at random read/write. The really low class cards are generally bottom of the bin chips, and the class 4 cards seem to be the most well balanced.

Second random performance factor is the unique setup that everyone is using. I use a recent version of haret that I compiled a couple of months ago while the one in reefer's packages is over a year old. Also, you never know what apps others have installed, and we just aren't comparing clean apples to clean apples if ya know what I mean
__________________
Reply With Quote
This post has been thanked 2 times.