[Touch Diamond, MDA Compact IV ROM Development] leeston2379:
This is not my work, just a copy of advice somewhere else in this thread though i can't find it now. Thanks to original poster.

Thought i'd repost as i've quoted this a few times.

You have stability issues or auto soft/hard-resets?

First to say: some other ROMs have the same problems! However, the many different issues mentioned in this thread,

like not booting devices, devices loosing their config after soft-reset,

devices stuck up in boot-screen or a booting-loop often have the same cause -

1. problems with internal storage management of the device (has nothing to do with the RAM issues often complained about here),

2. wrong flashing (HSPL etc.), 3. no hard-reset bevore/after flashing,

4. whatever... Please try the following workaround BEFORE you start complaining about your problems - I'm sure NRG would be grateful for that! My suggestion: Do that each time you flash an EnergyROM.

- Download mtty1_1_.42_538 on PC

- Do a hard-reset (hold vol-down + center (wheel) button + red soft-reset button)

- Restart device in bootloader (hold vol-down + red soft-reset button)

- Deactivate USB option on ActiveSync(PC): File -> Connection Settings -> Allow USB Connection

- Run mtty1_1_.42_538 on your PC, press USB on the right, followed by a RETURN inside the prompt window!

- You should see "CMD>" in the prompt. Type in "task 29" followed by RETURN!

- Close mtty1_1_.42_538 when process has finished!

- Reactivate USB option on ActiveSync(PC): File -> Connection Settings -> Allow USB Connection

- Flash a ROM of your choice within bootloader. Do not make a soft-reset before that, the old ROM won't start anymore!

- After flashing do a hard-reset (hold vol-down + center (wheel) button + red soft-reset button).

And when even flashing is not working (0% etc.), take a look at the sticky threads of this subforum!

You complain about low memory?

You are not alone man... but please stop it! This thread has already been cleaned by a mod because of that! This ROM contains apps, tools and some other stuff (TF3D2), that was ported from other devices with double the memory of our Diamond/MDA! So if the ROM eats your memory, do not complain about it, but deactivate some features, like phone canvas or even TF3D2! If you do not want to, use htcAddicts cleanRAM or look for an other ROM! You can't get the cake AND even eat it!

Your device seems to be unlocked after wakeup from sleep mode?

When the device was locked and put to sleep mode, the lockscreen disappears after wakeup. TF3D2 can be partially used and the device seems to be unlocked, but it's not - task bar does not work and the device sometimes stays dimmed! Seems that TF3D2 overlaps the WM6.5 lockscreen on wakeup! Try to fall back to WM classic lock screen when using TF3D2: Start->Settings->Lock->Display

You can't find the "Dim-Backlight-On-Unlock-Screen" option?

Well... it's missing. If Advanced Config does not work, try this registry change:

[HKEY_CURRENT_USER\ControlPanel\BackLight]

"DimBKLinUnlockScreen"=dword:00000000

You are missing the phone-keypad SIP or other keyboard languages on cooked-in EzInput/TouchInput 2.0?

If somebody is missing the old phone-keypad SIP known from EzInput 1.5, the currently cooked-in version does support it:

[HKEY_LOCAL_MACHINE\Software\HTC\ezsip]

"CurrentSIP"=dword:00000a00 ;Phone Keypad (formerly Compact QWERTY in previous versions)

"CurrentSIP"=dword:00000d00 ;Full QWERTY

The cooked-in version also has many T9 languages included, but the selectbox for changing them is missing in WM.

You first have to activate them all with the attached registry file. Then you can change the default language in the registry. I have not tried all of them, so you have to. And make a soft-reset after changing the layout and/or language, so that the SIP can reload all layout data!

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9]

"DefaultLanguage"=dword:00000101 ;Arabic - No phone-keypad layout!

"DefaultLanguage"=dword:00000105 ;Czech

"DefaultLanguage"=dword:00000106 ;Danish

"DefaultLanguage"=dword:00000107 ;German - Working

"DefaultLanguage"=dword:00000108 ;Greek - Working incl. greek layout

"DefaultLanguage"=dword:00000109 ;English - Working

"DefaultLanguage"=dword:0000010A ;Spanish

"DefaultLanguage"=dword:0000010B ;Finnish

"DefaultLanguage"=dword:0000010C ;French

"DefaultLanguage"=dword:0000010E ;Hungarian

"DefaultLanguage"=dword:00000110 ;Italian

"DefaultLanguage"=dword:00000113 ;Dutch

"DefaultLanguage"=dword:00000114 ;Norwegian

"DefaultLanguage"=dword:00000115 ;Polish

"DefaultLanguage"=dword:00000116 ;Portuguese

"DefaultLanguage"=dword:00000118 ;Romanian

"DefaultLanguage"=dword:00000119 ;Russian - No phone-keypad layout!

"DefaultLanguage"=dword:0000011B ;Slovak

"DefaultLanguage"=dword:0000011D ;Swedish

"DefaultLanguage"=dword:0000011F ;Turkish

You can't activate SMS delivery notification?

There are two different option menus where you can activate it. The first is on the TF3D2 skinned threaded view (Menu->Message Option). The second is on WM composer, but it's not accessible. To activate it you need to set the following registry value (maybe a roft-reset is needed!).

[HKEY_CURRENT_USER\Software\Microsoft\Inbox\Setting s]

"DisableSMSDeliveryReceipt"=dword:00000000

Now you can also access the option in WM composer (Menu->Message Option), what really works fine. The only strange thing is: on both composing views it has to be enabled each time you write a SMS. It's not saved when closing the threaded views/composer.

BTW: If you want to activate the SMS sent notification, set this registry key (works permanently for both composing views):

[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Settin gs]

"SMSNoSentMsg"=dword:00000000

Your TF3D2 clock is sometimes one hour off from the local time?

That seems to be a bug in the HTC world clock. However, here is a workaround:

- Open HTC world clock and set you local timezone and time.

- Then go to WM clock setup and correct the wrong timezone.

- Now WM and HTC world clock are "synced".

- But do not touch the HTC world clock anymore, or you'll have to fix it again!