[myTouch 3G, Magic Android Development] Reignzone:
Read this if you're experiencing issues:

Alright folks; I've noticed several of you have "reposted" topics regarding "known issues" both prior to my comments and shortly thereafter. Now, having said that I've decided to cover a few subjects; that way NO MORE confusion should take place. experiencing

KNOWN ISSUES:

- BFS-patches higher than the "230" version WILL cause virtual memory crashes due to the pre-installed RAM hack.

- CompCache modules (might be) are missing or the files are incorrectly organized. Therefore, you might experience a CC error when using the ADB command.

(TIPS & TRICKS) WAYS TO PREVENT BOGGLING DOWN YOUR DEVICE:

* Use the application known as, "Move Cache for Root Users".

* Use a "task managing" application of your choice to "free-up" available memory by ENDING foreground and background applications. DO THIS ONCE EVERY COUPLE OF HOURS! Be sure to "exclude" the programs that are essential to the ROM; or must be running at all times. For instance; TouchFLO, Touch Input, etc.

* If you begin to experience a serious amount of latency while browsing the web, transferring from home screen to home screen, or during multi-tasking within the applications drawer: OPEN YOUR TASK MANAGER & END ALL! I suggest performing an "end all" command once every 3-4 hours in order to prevent "too much" background data synchronization. This can also increase the overall expectancy of your battery life.

* Organize your home screens based on what is actually necessary; versus "making it look cool" by loading every screen with widgets, shortcuts, and live folders. If you do not use all seven home screens; so be it! They aren't necessary. I only utilize THREE, which is plenty for the widgets that I need to have running; along with my most commonly used applications.

* Use the OVERCLOCK WIDGET instead of SetCPU to adjust your frequency sampling of the device's processor. EXCLUDE this application within your TASK MANAGER so it does not get "killed", because it MUST BE RUNNING in order to accurately provide the increase of MHz performance. Set the minimum frequency to 328MHz; while the maximum should be raised to 528MHz. Change the UPDATE INTERVAL to 5-10 seconds. This will allow the frequencies to alter themselves much faster than updating them manually according to device usage. Select SUPPRESS NOTIFICATION, that way the notification does not appear on your screen when the frequencies are changed periodically. (You'll thank me later)

* If you're primary desire is to "save battery life", a little tip such as this might be of some help: DISABLE BACKGROUND DATA SYNCHRONIZATION within the device settings. This will prevent your e-mail from refreshing automatically; along with various other applications being prevented from "updating" simultaneously on their own. Personally; I refresh every home screen widget, e-mail application, and data retrieval service MANUALLY! That's my preference, because I know when I'd like to "check" the status of things...I don't need my device to do that for me!

* Use Servo Search or AURORA Device Search as a universal search program for your device. This will also make-up for the fact that you experience a FORCE CLOSE while attempting to access the PEOPLE SEARCH function within your contacts. DO NOT CONTINUE TO COMPLAIN ABOUT THIS ISSUE! It's a problem involving the kernel; not the ROM. Enjoy the responsiveness and stability; don't be so concerned and bothered by the "little things" such as that!

* Perform a REBOOT via ADB or by powering down your device ONCE every 9-12 hours! After powering down; leave the device off for a few minutes so it can "relax".

* Remove the battery from your device ONCE a day. Whether this is how you're performing the reboot does not matter...I merely suggest that this still be done. Keep the battery out of your device for apporximately TWO MINUTES and HOLD DOWN the POWER KEY during this time period. This will assist the device in clearing "static electricity build-up" within the hardware.

* Clear the dalvik-cache (from SD) if you have moved "all cache to SD". I suggest Amon_RA's latest recovery image to perform this task directly from the options menu.

* DOWNLOAD THE NON-A2SD VERSION of "any" ROM! That way; you can ODEX your applications to provide a theoretical "boost of speed" in responsiveness and performance.

* If you experience a RANDOM REBOOT or your device will NOT "wake from a sleep-state", remove the battery for a few minutes, then insert it once again. The decision made on "what to do" at that point is entirely up to you! However, I would suggest applying a different kernel to your ROM, or perhaps WIPING and re-flashing the same build.

* If you're experiencing numerous force closes while trying to access several different applications; there are a few potential "fixes" to resolve this issue. The first being, reboot into recovery mode...and fix package mismatches. After that process has completed; repair the extension file systems. Then REBOOT your device normally. If you do not wish to reboot in recovery mode (for whatever reason) power down your device and reboot it while holding down the MENU BUTTON and POWER! This will offer a temporary fix for those pesky force closes at start-up! Finally, last...but certainly not least: RUN the FIX_PERMISSIONS command via terminal emulator.

* To "enable" your LED notifications...use the application known as, "Missed Call" or perhaps "Missed Reminder". These can be used to alter the repeat intervals, colors, and various user settings for the LEDs. EVERY COLOR IS OPERATIONAL! Trust me, I've tried them all...and use this application DAILY!

* Does the ROM appear to be running a little "too laggy" for you? I would suggest that you REBUILD YOUR PARTITIONS MANUALLY. WIPE, repair extension files, WIPE, then re-flash the ROM once more. This will resolve 90% of latency issues at start-up and during basic usage.

* Is there not enough home screen responsiveness? Well, there certainly can be...and this can be achieved by increasing your "SWAP SPACE". Now, by this I'm referring to adjusting the size of your Linux-swap partition. My preference is 192MB of swap space with the swappiness percentage set to 80%. If you believe that 192MB is "overkill", I would recommend that you try 128MB instead.

* Adjust your user.conf and push it via ADB command. This will prevent any further confusion with understanding "Reignzone's settings" and your own!

* Are you having trouble with the ALARM CLOCK not functioning properly? Perhaps it does not "go off" when it's set to, isn't loud enough, or maybe even "goes off" a little too late? There is a simple solution for this problem. Upon opening your Alarm Clock application or the standard Clock...set your alarm as you normally would. Be sure to enable a notification and adjust the interval of reminders or repeating. Now, exit the application and open your TASK MANAGER. Locate your "Alarm Clock" or "Clock" application and EXCLUDE it so that it REMAINS OPEN AND RUNNING in the background. This should allow it to "launch" when prompted to "go off" as an alarm.

* Did your ringtones and notifications "stop" responding or refuse to play in their entirety? Well, like most issues...this can be solved by rebooting. Typically; the time period in which these issues might occur is a few hours. Then again, if you're like myself...and text message a lot or receive a higher amount of calling traffic, you can expect this within an hour or so.

* Bluetooth does work; it will pair, but not necessarily provide audio of any kind during a phone call. I've managed to pair it with a Toyota Prius, including operative voice data transfers. As for headsets; do not expect the same results; yet!

* If you're having any trouble with Wireless Tether for Root Users (v1.60 HTC-pre 3) allow the application to install the required binaries and various files to allow the tethering to register between connections. Bluetooth tethering is functional as well. Hence the reason that I felt the need to address the Bluetooth issue.

* Is your device having trouble "waking from the sleep state" after the screen dims? Pulling the battery will always resolve this issue...it's unfortunate that this is the only solution that doesn't involve patching a new kernel over your build. Otherwise, as I've stated previous; applying a new kernel patch, more specifically the BFS-230 kernel will repair 90% of problems caused by virtual memory crashes.

* Are you having issues with data or "3G" connectivity? Be sure that your APN settings are set properly to link your device to the T-Mobile USA frequencies for data services. In coordination with that; adjust your LOCALE SETTINGS to further synchronize the time & date settings of your device. That will be most helpful if you are unable to immediately recognize the network after flashing a new ROM.

ALRIGHT; there you have it folks...hopefully this has assisted the masses in some way, shape, or form! Please, excuse any typos or grammatical errors; and for those of you who might have questions in the near future, please refer back to this post. If deemed necessary, bump this post and suggest it to those who are in need of a little help. :D

Best wishes.