[Desire Q&A, Help & Troubleshooting] infozerich:
Some ROMs require the use of a custom HBOOT such as CM7r2. Other ROMs can make use of a swap partition. I'm interested in knowing if you have installed these ROMs with stock HBOOT or have changed to custom HBOOTs. It's a critical component that sets the sizes of the system, cache and data partitions.

Try holding the volume-down button and the power button simultaneously when powering on your device for information about the HBOOT to be displayed.

Perhaps the errors are caused due to insufficient space on these partitions as these tend to grow after awhile. To confirm, from a Terminal, type: df

This should display the available and currently occupied space of the filesystem.

The V6 Supercharger script will have an option to modify the kb_read_ahead value to increase the read-cache, and if enabled, should result in an increase in read/write speeds for the sdcard. Furthermore, the script has options that should help with the freezing as it frees up more RAM (options 2-10).

A summary of the undervolting and overclocking section would be that undervolting conservatively will result in savings in battery consumption, but extreme undervolting will result in more power consumption by having to correct the inadequate values set plus rebooting. On the other hand, overclocking can lead to instability if the device overheats.

The swap partition may be used by the ROM you have flashed. Has the sdcard been partitioned according to the developer's specifications with each flash? I mention this because some ROMs make use of INT2SD or DATA++ which makes use of swap. If you plan to only use A2SD, having no swap is fine.

Try using ADB if you have it installed.

adb logcat *:E > /sdcard/error_log.txt

Otherwise, that logcat is acceptable, but I will need to know more about the stability issues and when these occur to properly cross-reference the logs and events.

Excellent. I've been wondering. Have you tried formatting the sdcard and only having the ROM zip file on the sdcard and flashing only that? I'd like to know if there are settings in EXT4 that may be causing problems later on.

It's best practice and highly recommended. On a Windows OS, you can try MultiHasher. There are many open-source applications available.

By problems do you mean random reboots and the phone being unresponsive? I'd really like to see the output of terminal: df. Also, do you flash the ROM first and immediately flash GApps afterward? Sometimes the GApps being flashed takes up all the space on the system partition and causes a myriad of problems. There is a minimal GApps version by LaidbackNikez and vinjendrahs ROMs that have GApps integrated.

Both ROMs make use of the stock HBOOT.

Good to know. You aren't restoring backups are you? It's really important we work on a clean slate to narrow down the source of the problem.

If the phone is unstable after flashing these ROMs under controlled conditions, and extenuating issues from configuration files residing on the sdcard are eliminated, that leaves us with considering hardware faults.

I'm curious to know if you are using a 1400 mAh Lithium-ion 3.7V battery. Also, is the phone unstable if you remove the sdcard and run the phone without it?

If all else fails, reverting to stock and verifying that issues persist will point to the most likely suspect. Also, some ROM developer specify EXT3 as the filesystem of choice, but seeing as you have the 4EXT Recovery, converting it will be a simple matter.

We'll have to test out the areas that are causing you the most trouble. I'm looking into the A2SD script and seeing where problems may arise. Let's clarify the free space on the filesystem first and then we'll tackle the sdcard. Alternatively, you can try croniccorey's INT2SD scripts which are flashable through recovery. You just have to flash it after you flash the ROM and a script will be placed in /etc/init.d to take care of the rest. No need to manually activate or type anything in a terminal.

Finally, flashing different ROMs can make troubleshooting more difficult to pinpoint the problem. However, if you intend to fix it, here are a list of prompts you can follow.

If it's a device issue, reverting to stock should clarify the matter. If it's a rooting issue, I'd need to know if these issues started occurring before or after rooting via revolutionary. If it's the sdcard at fault, you can test it by running the smartphone without the sdcard mounted (after flashing a ROM and rebooting, run it without the sdcard inside), or physically replace it with another sdcard, e.g. a 2GB Sandisk sdcard would work just fine.