[G1 Android Development] nitor:
Yarggh, my android's gotten the bends..

Hey all,

I've been keeping track of this for a while, switched to TheDude's 1.1a several days ago and have had consistent crashing issues in the Application Management, Quick Launch, and other tasks that involve loading the entire list of apps (except the Market, oddly enough). I didn't want to have to post, but I can't find any information of such an issue anywhere-- and I doubt that I'm the only one experiencing it.

Initially I believed this to be the fault of apps2sd, as I updated the image incorrectly to the newest a2sd.sh and got loads of inode errors on the filesystem. Each time I'd run e2fsck and plug the card back in, I'd be able to load the above activities just fine.

I solved that problem, wiped, updated, wiped again, updated a2sd.sh, and it was all smooth-- until I approached 200 apps. Even though there were no longer inode errors, I got the crashes again. I removed a couple of apps via the market that took up resources upon start (such as weatherbug), and the problem went away. Now I went through the market again and got the rest of what I wanted (probably too much at once, but none required resources on startup), and the issue is back.

I'm currently going through with Advanced Task Manager and shutting off all the processes one by one to see if I could locate the culprit-- or at least, one of the contributing factors. I've currently got app and app-private in /system/sd/. I'll remove app-private and get its stuff back in the intmem directory and see if it helps.

Is this a bug in the current apps to sd method, or in the application management of android itself? Is there a way that I can listen with adb as this is going on? I feel that only the top, java layer of the system is locking, not the stuff undernstart (eath (and I do lose response in the buttons, the keyboard backlight doesn't come on, etc.)

I'm eager to help iron this one out. It's pissing me off.

EDIT @ +5mins: I rebooted and killed all the running processes (bluebrush, mixzing, tunewiki, etc.), and was able to get into the Quick Launch activity, but it's absolutely ground to a halt. I cannot scroll, and if I flip the screen it seems to rotate about a minute later. After a few minutes, the phone rebooted to the Android scrolling screen. Not sure where that is in the startup scripts. I'm going to try moving the private apps next. This is really starting to look like an Android upstream bug. =(

EDIT @ +70mins: I used adb to move the contents of /system/sd/app-private over to /system/intmem/app-private, removed the directory on the sd card, and rebooted. Well, it worked.. until I reinstalled all the resource-hogging-on-startup apps (simchecker, where's my android, toggle settings, etc.). I rebooted, and the crash was back.

I'm rebooting again, and will report which app, exactly, is causing this issue. Though it is quite possible that it is simply a combination error-- this thing doesn't have that much ram.. =\

EDIT: It didn't seem to work. Now I'm quite confused. Can someone give me a line that would allow me to watch the events through adb? Argh.

Also, does anyone know what determines whether an app runs on startup or not? Is it an init script? There really is no purpose for all of this crap to run before the apps are opened by the user.

EDIT: Gah, if I first click Application Management, and let it load, then Quick Launch does as well. Otherwise, it reboots.